#31999 closed defect (fixed)
indi: conflicting types for 'closeDome'
Reported by: | fcasarramona | Owned by: | jtomshine@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
Port: | indi |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Trying to install indi port in a 10.7.2 OSX the following compiling error is logged:
:info:build /opt/local/var/macports/build/_Users_Alnair_ports_science_indi08/indi/work/libindi-0.8/examples/tutorial_dome.c:185:6: error: conflicting types for 'closeDome'
Complete log file is attached.
Attachments (1)
Change History (15)
comment:1 Changed 13 years ago by fcasarramona
comment:2 follow-ups: 3 4 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to jtomshine@… |
---|---|
Summary: | tutorial_dome.c don't compile → indi: conflicting types for 'closeDome' |
The log you attached is incomplete (clean and try again to generate a complete log) but it looks like you're using clang. Have you tried llvm-gcc-4.2 instead? See wiki:ProblemHotlist#compiler.
Somebody should file a bug report with the indi project: http://sourceforge.net/tracker/?group_id=90275&atid=593019
comment:3 Changed 13 years ago by fcasarramona
Replying to ryandesign@…:
The log you attached is incomplete (clean and try again to generate a complete log) but it looks like you're using clang. Have you tried llvm-gcc-4.2 instead? See wiki:ProblemHotlist#compiler.
Somebody should file a bug report with the indi project: http://sourceforge.net/tracker/?group_id=90275&atid=593019
There are other users with OSX 10.7.2 than could compile without problems. I will check with them.
comment:4 Changed 13 years ago by fcasarramona
Replying to ryandesign@…:
The log you attached is incomplete (clean and try again to generate a complete log) but it looks like you're using clang. Have you tried llvm-gcc-4.2 instead? See wiki:ProblemHotlist#compiler.
Good, with llvm-gcc-4.2 compiles ok.
Can you change port file in order to configure llvm-gcc-4.2 as compiler?
Thanks.
comment:5 follow-up: 6 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:6 Changed 13 years ago by fcasarramona
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:7 follow-up: 8 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | reopened → closed |
One does not use an "=" in Tcl when setting a variable. The block I inserted into the portfile is copied directly from wiki:PortfileRecipes#compiler and works correctly.
comment:8 follow-up: 9 Changed 13 years ago by fcasarramona
Replying to ryandesign@…:
One does not use an "=" in Tcl when setting a variable. The block I inserted into the portfile is copied directly from wiki:PortfileRecipes#compiler and works correctly.
Ok, but it doesn't work to me. The same error when compiling. However if I do "sudo port install indi configure.compiler=llvm-gcc-4.2" it works fine.
By the way, the user who can install with 10.7.2 hase XCode 4.1 installed, not 4.2
comment:9 follow-up: 10 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to ferran.casarramona@…:
Ok, but it doesn't work to me. The same error when compiling. However if I do "sudo port install indi configure.compiler=llvm-gcc-4.2" it works fine.
Did you "sudo port selfupdate
" and "sudo port clean indi
"?
By the way, the user who can install with 10.7.2 hase XCode 4.1 installed, not 4.2
Yes, the default compiler MacPorts chooses for Xcode 4.0 and 4.1 is llvm-gcc-4.2, and for Xcode 4.2 it's clang.
comment:10 Changed 13 years ago by fcasarramona
Replying to ryandesign@…:
Replying to ferran.casarramona@…:
Ok, but it doesn't work to me. The same error when compiling. However if I do "sudo port install indi configure.compiler=llvm-gcc-4.2" it works fine.
Did you "
sudo port selfupdate
" and "sudo port clean indi
"?
Yes, I did.
Also I verified the new code was in my local port tree.
comment:11 follow-up: 12 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Hmm, I can't explain that. Can you selfupdate and clean and try again one more time, and attach the new main.log?
comment:12 Changed 13 years ago by fcasarramona
Replying to ryandesign@…:
Hmm, I can't explain that. Can you selfupdate and clean and try again one more time, and attach the new main.log?
I replaced the main.log file for a new one.
comment:13 follow-up: 14 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
I think you have a local copy of the old indi portfile in /Users/Alnair/ports/science/indi08.
comment:14 Changed 13 years ago by fcasarramona
Replying to ryandesign@…:
I think you have a local copy of the old indi portfile in /Users/Alnair/ports/science/indi08.
That's it. I apologize.
Thanks.
Another user has experienced the same bug in indi mailing list. Same 10.7.2 OSX version, and XCode just installed from AppStore.