From: Grzegorz J. <ja...@ac...> - 2004-07-26 16:04:15
|
Hi, Grigorenko Dmitriy wrote: >>>>/bin/bash ./libtool --mode=link g++ -g -O2 -o libocc.la -rpath >>>>/usr/local/lib empty_libocc.lo opencxx/libocc_mop.la > > libltdl/libltdl.la > >>>>mkdir .libs >>>>libtool: link: warning: undefined symbols not allowed in > > i686-pc-cygwin > >>>>shared libraries >>> >>>Is there a way to learn what undefined symbols are left??? (On Linux >>>there is 'nm', I don't know how to do this on Cygwin.) > > Here is the output: > > Dima@home ~/opencxx.pch > $ /bin/bash ./libtool --mode=relink g++ -g -O2 -o libocc.la -rpath > /home/Dima/ > opencxx.pch/testbed/lib empty_libocc.lo opencxx/libocc_mop.la > libltdl/libltdl.la > libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin > shared libraries > ar cru .libs/libocc.a empty_libocc.o > ranlib .libs/libocc.a > creating libocc.la > (cd .libs && rm -f libocc.la && ln -s ../libocc.la libocc.la) > > Dima@home ~/opencxx.pch > $ ./libtool --help --mode=relink > libtool: invalid operation mode `relink' > Try `libtool --help' for more information. > > Dima@home ~/opencxx.pch > $ ./libtool --version > ltmain.sh (GNU libtool) 1.5.6 (1.1220.2.94 2004/04/10 16:27:27) > > Copyright (C) 2003 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > Which file do I have to check? > As far as I understand, libocc.a is OK. All .(l)o and .(l)a files on the linker command line. > Dima@home ~/opencxx.pch > $ cd .libs/ > > Dima@home ~/opencxx.pch/.libs > $ nm libocc.a > > empty_libocc.o: > 00000000 b .bss > 00000000 d .data > 00000000 N .stab > 00000000 N .stabstr > 00000000 t .text > > > >>>>Tests do not work :(. See tester2.log for more details. >>> >>>This I don't understand. Libtool says it cannot find configure.ac or >>>configure.in. WHY??? Why on earth should it need these files??? >>>tester2.log shows the libtool command that failed. Could you check what >>>happens if you just use this command on its own? > > > I do not know why it is. > > Dima@home ~/opencxx.pch/testsuite/testsuite.dir/comp/tnested/compilation > $ libtool --tag=CXX --mode=compile --silent g++ -c tnested-class.2.ii -o > tnested-class.lo > libtool: Couldn't find configure.ac nor configure.in file Looks like a bug in cygwin. Seemingly workaround is available, see: http://www.cygwin.com/ml/cygwin/2002-01/msg01040.html BR GJ > > Dima@home ~/opencxx.pch/testsuite/testsuite.dir/comp/tnested/compilation > $ libtool --version > ltmain.sh (GNU libtool) 1.5.6 (1.1220.2.95 2004/04/11 05:50:42) > > Copyright (C) 2003 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > -------------------------------------------------------- > ltmain.sh (GNU libtool) 1.4.3 (1.922.2.110 2002/10/23 01:39:54) > -------------------------------------------------------- > This is libtool-wrapper, which will hand off execution > to one of the two real versions listed above, depending > on the contents of configure.in/configure.ac. Since the > wrapper was called from within a directory in which those > files are not found, this generic 'version' message is > displayed. > > Dima@home ~/opencxx.pch/testsuite/testsuite.dir/comp/tnested/compilation > $ |