Zak Mc Kracken wrote:
libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' This problem is since the change to "/usr/bin/gcc-4.0" for CC. Switching compiler back to "gcc" (or "gcc-4.0") makes it work. Something like: port build configure.cc=gcc configure.cxx=g++
Please, could someone explain what "port build configure.cc=gcc configure.cxx=g++" means? Do I have to downgrade gcc? How?
If the problem is that libtool thinks the compiler is "gcc", and macports is passing "/usr/bin/gcc-4.0" instead - then it can be worked around by adding similar such parameters: sudo port build apache2 configure.cc=gcc configure.cxx=g++ Or you can try rebuilding libtool, as suggested elsewhere.
I have been trying to have apache2 + php5 + mysql5 working on my Mac for two days. I think changes to a resource like port should be made only after extensive testing (or am I using an unstable version?). It's all so frustrating...
Sorry to hear that. I think the change was made for 1.5.1. --anders
On Feb 4, 2008, at 12:03, Anders F Björklund wrote:
Zak Mc Kracken wrote:
libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' This problem is since the change to "/usr/bin/gcc-4.0" for CC. Switching compiler back to "gcc" (or "gcc-4.0") makes it work. Something like: port build configure.cc=gcc configure.cxx=g++
Please, could someone explain what "port build configure.cc=gcc configure.cxx=g++" means? Do I have to downgrade gcc? How?
If the problem is that libtool thinks the compiler is "gcc", and macports is passing "/usr/bin/gcc-4.0" instead - then it can be worked around by adding similar such parameters: sudo port build apache2 configure.cc=gcc configure.cxx=g++
Or you can try rebuilding libtool, as suggested elsewhere.
libtool's revision has been bumped so that everyone will be forced to rebuild it so that this problem should disappear.
I have been trying to have apache2 + php5 + mysql5 working on my Mac for two days. I think changes to a resource like port should be made only after extensive testing (or am I using an unstable version?). It's all so frustrating...
Sorry to hear that. I think the change was made for 1.5.1.
I thought the change was made for 1.6.0? Anyway, MacPorts is developed by a small team of volunteers. Nobody's getting paid to do this work. There isn't an extensive network of testers. When stuff breaks, we try to fix it. We do the best we can.
Ryan Schmidt wrote:
I think the change was made for 1.5.1.
I thought the change was made for 1.6.0?
http://trac.macports.org/projects/macports/changeset/27018 Doesn't matter... --anders
On Feb 4, 2008 10:33 AM, Ryan Schmidt <ryandesign@macports.org> wrote:
libtool's revision has been bumped so that everyone will be forced to rebuild it so that this problem should disappear.
This is confusing to me, since the libtool that is crapping out is ./libtool (relative to the port's build directory). Where does the ports-installed libtool enter into it? Interestingly, I just found that libidl built without issue on another system here (also PPC, also 10.4.11). kitchen:~ root# port installed | grep libidl libidl @0.8.10_0 (active) This makes me wonder why two systems are having issues and one isn't. G4 good, G5 bad: also the G4s have been using MacPorts for quite awhile (since it was DarwinPorts). Could there be some conflicting cruft in there somewhere? -- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@gmail.com>
participants (3)
-
Anders F Björklund
-
paul beard
-
Ryan Schmidt