Re: libtool problem
> > > > I am trying to compile pango on HPUX-11.22 (IA64) platform using gcc-3.3.1. > > > > Pango first generates "libpango.so", Then it generates another library > > "libpangox.so" that links to "libpango.so". > > > > shared library list: > > ./.libs/libpango.so > > libX11.so.1 > > libc.so.1 > > > > as you see from the above it links to " ./.libs/libpango.so". This has > > caused lot of problem. > > Is this the result when libpangox.so is created or *after* it is > installed? What matters is the result after installation. No, this is the result "before" libpangox.so installed. I take your point, But some packages ( such as pango , gtk+2, ... ) are building library first, and then they use that library to build an executable. In a cases such as above programs, the program will fail to build the executables in compile time. Even before they get to install phase. Thanks __Mehdi > > -- > albert chin ([EMAIL PROTECTED]) > ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Problem running 'make check' with fort77 installed
Hi, I'm currently trying to build a patch for my -no-static proposal (see my previous e-mail). So the first thing I did was to perform a cvs checkout of libtool and tried a 'make' and (for the first time) a 'make check'. The 'make check' resulted in a total process starvation on my system for the first test it performed. After some digging I found out the reason: - when you issue a 'make check', first a ./configure is performed in the cdemo directory. - one of the tests that is performed by configure is to verify whether for fort77 (which is available on my system) the PIC flag -fno-common works. - it seems that when fort77 is called to compile conftest.f the environment variable 'CC=fort77' is set. - Since fort77 is a script which uses the CC environment variable to call the C compiler the script now starts calling itself recursively and therefore totally starves my system of process resources. Strangely enough the CC=fort77 environment setting does not appear to the fort77 script when you call './configure' from the command prompt. It only appears when ./configure is called via a 'make test'. I was not able to find out what precisely triggers the passing of the CC environment variable when '(eval "$lt_compile" 2>conftest.err)' is called, but it sure seems like a bug of some sort to me that this can occur. FYI, I'm using the following: platform: Mac OS X 10.2.6 autoconf: 2.57 automake: 1.7.6 libtool (installed version): 1.5 (1.1220 2003/04/05 19:32:58) libtool (cvs version, on which I performed the 'make check'): 1.5a (1.1243 2003/07/15 00:05:21) fort77: latest version as retrieved through fink Regards, Sander Niemeijer ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: libtool problem
On Mon, Jul 28, 2003 at 08:45:00AM +0100, M. Lavasani wrote: > > > > > > > I am trying to compile pango on HPUX-11.22 (IA64) platform using gcc-3.3.1. > > > > > > Pango first generates "libpango.so", Then it generates another library > > > "libpangox.so" that links to "libpango.so". > > > > > > shared library list: > > > ./.libs/libpango.so > > > libX11.so.1 > > > libc.so.1 > > > > > > as you see from the above it links to " ./.libs/libpango.so". This has > > > caused lot of problem. > > > > Is this the result when libpangox.so is created or *after* it is > > installed? What matters is the result after installation. > > No, this is the result "before" libpangox.so installed. Then it is correct. > I take your point, But some packages ( such as pango , gtk+2, ... ) > are building library first, and then they use that library to build > an executable. > > In a cases such as above programs, the program will fail to build > the executables in compile time. Even before they get to install > phase. Run 'make install' and you'll see that libtool relinks the binaries/libraries so the end result is ok. I've built GTK+ 2.2.x fine on HP-UX 11.00 and 11i. -- albert chin ([EMAIL PROTECTED]) ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Don't wait for rates to climb back up
tjr627079c9z96tvg7f5pq14616m255et45383p3m7mt6sj7gdg1q7d03wl5w4ir801zpyc97j09288ft78ndm7638659554h34b7932bv2i5g9q 67864676zjy7255et45383p3m7mt6sj7gdg1q7d00502kf74824oen1w69x898u85prc3aok3wl5w4ir801z pyc97j09288ft78ndm7638659554h34b7932bv2i5g9q67864676zjy7 255et45383p3m7mt6sj7gdg1q7d00502kf74824oen1w69x898u85prc 3aok3wl5w4ir801zpyc97j09288fTo remove yourself from our opt in list Press Here!eXZvAHx8eU10ewA7fH90 67864676zjy7255et45383p3m7mt ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
