Anyone else seeing this? /bin/sh ./libtool --tag=CC --mode=link /usr/bin/gcc-4.0 -O2 -no-cpp-precomp -version-info 0:0:0 -L/opt/local/lib -lglib-2.0 -lintl -liconv -no-undefined -L/opt/local/lib -o libIDL-2.la -rpath /opt/local/lib parser.lo lexer.lo ns.lo util.lo /usr/bin/gcc-4.0 -dynamiclib -o .libs/libIDL-2.0.0.0.dylib .libs/parser.o .libs/lexer.o .libs/ns.o .libs/util.o -L/opt/local/lib /opt/local/lib/libglib-2.0.dylib /opt/local/lib/libintl.dylib /opt/local/lib/libiconv.dylib -install_name /opt/local/lib/libIDL- 2.0.dylib -compatibility_version 1 -current_version 1.0 ld: Undefined symbols: ___IDL_cur_token_line ___IDL_lex ___IDL_prev_token_line ___IDL_in ___IDL_lex_cleanup ___IDL_lex_init /usr/bin/libtool: internal link edit command failed make[2]: *** [libIDL-2.la] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 This on a PPC machine running Tiger, Xcode as current as can be for that platform. gnome-platform-suite depends on libidl firefox-x11 depends on libidl gnome-vfs depends on libidl orbit2 depends on libidl -- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@gmail.com>
paul beard wrote:
Anyone else seeing this?
/bin/sh ./libtool --tag=CC --mode=link /usr/bin/gcc-4.0 -O2 -no-cpp-precomp -version-info 0:0:0 -L/opt/local/lib -lglib-2.0 -lintl -liconv -no-undefined -L/opt/local/lib -o libIDL-2.la -rpath /opt/local/lib parser.lo lexer.lo ns.lo util.lo /usr/bin/gcc-4.0 -dynamiclib -o .libs/libIDL-2.0.0.0.dylib .libs/parser.o .libs/lexer.o .libs/ns.o .libs/util.o -L/opt/local/lib /opt/local/lib/libglib-2.0.dylib /opt/local/lib/libintl.dylib /opt/local/lib/libiconv.dylib -install_name /opt/local/lib/libIDL-2.0.dylib -compatibility_version 1 -current_version 1.0 ld: Undefined symbols: ___IDL_cur_token_line ___IDL_lex ___IDL_prev_token_line ___IDL_in ___IDL_lex_cleanup ___IDL_lex_init /usr/bin/libtool: internal link edit command failed make[2]: *** [libIDL-2.la] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2
This on a PPC machine running Tiger, Xcode as current as can be for that platform.
Yes - I am getting something like this too. My version is as follows: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< port upgrade libidl ---> Building libidl with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_libidl/work/libIDL-0.8.10" && make all " returned error 2 Command output: make all-recursive Making all in include Making all in libIDL make all-am make[4]: Nothing to be done for `all-am'. make[3]: Nothing to be done for `all-am'. /bin/sh ./libtool --tag=CC --mode=link /usr/bin/gcc-4.0 -O2 -no-cpp-precomp -version-info 0:0:0 -L/opt/local/lib -lglib-2.0 -lintl -liconv -no-undefined -L/opt/local/lib -o libIDL-2.la -rpath /opt/local/lib parser.lo lexer.lo ns.lo util.lo /usr/bin/gcc-4.0 -dynamiclib -o .libs/libIDL-2.0.0.0.dylib .libs/parser.o .libs/lexer.o .libs/ns.o .libs/util.o -L/opt/local/lib /opt/local/lib/libglib-2.0.dylib /opt/local/lib/libintl.dylib /opt/local/lib/libiconv.dylib -install_name /opt/local/lib/libIDL-2.0.dylib -compatibility_version 1 -current_version 1.0 ld: Undefined symbols: ___IDL_cur_token_line ___IDL_lex ___IDL_prev_token_line ___IDL_in ___IDL_lex_cleanup ___IDL_lex_init /usr/libexec/gcc/i686-apple-darwin8/4.0.1/libtool: internal link edit command failed make[2]: *** [libIDL-2.la] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Unable to upgrade port: 1
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is on an Intel-based MacBookPro running Tiger with everything as up to date as possible. XCode is version 2.5
I have been trying to follow the discussions on libtool woes but it looks as if this is a different problem. Anyone have any ideas on fixing it. Thanks to all David Rowe
On Feb 5, 2008 2:35 PM, David Rowe <david.rowe@freeuk.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is on an Intel-based MacBookPro running Tiger with everything as up to date as possible. XCode is version 2.5
I have been trying to follow the discussions on libtool woes but it looks as if this is a different problem.
Anyone have any ideas on fixing it.
Thanks to all
David Rowe
Looks like it has been worked around: try a fresh sync of your ports tree and see what happens. Worked for me™ -- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@gmail.com>
On Feb 5, 2008 paul beard wrote:
On Feb 5, 2008 2:35 PM, David Rowe <david.rowe@freeuk.com <mailto:david.rowe@freeuk.com>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is on an Intel-based MacBookPro running Tiger with everything as up to date as possible. XCode is version 2.5
I have been trying to follow the discussions on libtool woes but it looks as if this is a different problem.
Looks like it has been worked around: try a fresh sync of your ports tree and see what happens. Worked for me™
No luck - I tried port sync and even port selfupdate, but I still get the same problem Thanks for the suggestion David Rowe
On Feb 5, 2008, at 18:35, David Rowe wrote:
On Feb 5, 2008 paul beard wrote:
On Feb 5, 2008 2:35 PM, David Rowe wrote:
This is on an Intel-based MacBookPro running Tiger with everything as up to date as possible. XCode is version 2.5
I have been trying to follow the discussions on libtool woes but it looks as if this is a different problem.
Looks like it has been worked around: try a fresh sync of your ports tree and see what happens. Worked for me™
No luck - I tried port sync and even port selfupdate, but I still get the same problem
The problem has not been worked around. The bug is still open: http://trac.macosforge.org/projects/macports/ticket/14144 The problems that were worked around were the "unable to infer tagged configuration" bug affecting apache2, mjpegtools and possibly others. These were fixed by bumping the revision of apr and libtool to force their rebuild. The libidl bug is a different and unrelated bug. libidl is unmaintained so someone will have to volunteer to figure out what's breaking, and how to fix it. Actually, Tod Morrison just posted in the bug that he found a reason why it's failing, and a workaround, but not yet a fix that we can apply to the portfile.
On Feb 5, 2008 6:14 PM, Ryan Schmidt <ryandesign@macports.org> wrote:
The problem has not been worked around. The bug is still open:
http://trac.macosforge.org/projects/macports/ticket/14144
The problems that were worked around were the "unable to infer tagged configuration" bug affecting apache2, mjpegtools and possibly others. These were fixed by bumping the revision of apr and libtool to force their rebuild.
The libidl bug is a different and unrelated bug. libidl is unmaintained so someone will have to volunteer to figure out what's breaking, and how to fix it. Actually, Tod Morrison just posted in the bug that he found a reason why it's failing, and a workaround, but not yet a fix that we can apply to the portfile.
howsomever, it upgraded just fine two days ago: I assumed it was fixed. The following ports are currently installed: libidl @0.8.10_0 (active) -- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@gmail.com>
participants (3)
-
David Rowe
-
paul beard
-
Ryan Schmidt