[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libtool : .o files are ignored when mixing .lo and .o files

From: Nicolas PENINGUY
Subject: Re: libtool : .o files are ignored when mixing .lo and .o files
Date: Sun, 21 Nov 2010 23:48:26 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101103 Fedora/1.0-0.33.b2pre.fc14 Thunderbird/3.1.6

On 11/21/2010 08:30 PM, Bob Friesenhahn wrote:
Libtool does not have knowledge of how stap_probes.o is built so it assumes that it is suitable for static linkage only. The same is true for .a archive files not built by libtool. This is intentional behaviour.

Sorry I'm a bit confused because glib does the same thing to build a shared library and the extern object file gobject_probes.o is included in the "gcc -shared" command line :

/bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -Wall -Wl,-Bsymbolic-functions -version-info 2704:0:2704 -export-dynamic -export-symbols-regex "^g.*" -o libgobject-2.0.la -rpath /usr/local/lib gatomicarray.lo [...] *gobject_probes.o*

*** Warning: Linking the shared library libgobject-2.0.la against the non-libtool
*** objects  gobject_probes.o is not portable!


libtool: link: gcc -shared .libs/gatomicarray.o [...] *gobject_probes.o* [...] -o .libs/libgobject-2.0.so.0.2704.0

How can libtool assume that gobject_probes.o is suitable for inclusion in a shared library (glib's case) and not for an "ar" archive (my case) ?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]