GNU bug report logs - #8481
linking with externally generated objects

Previous Next

Package: libtool;

Reported by: Nikos Mavrogiannopoulos <nmav <at> gnutls.org>

Date: Tue, 12 Apr 2011 03:48:02 UTC

Severity: normal

Full log


View this message in rfc822 format

From: Nikos Mavrogiannopoulos <nmav <at> gnutls.org>
To: 8481 <at> debbugs.gnu.org
Subject: bug#8481: linking with externally generated objects
Date: Mon, 11 Apr 2011 19:18:23 +0200
[Message part 1 (text/plain, inline)]
Hello,
 I use yasm to generate some objects and I want to include
them into a (static) library using libtool. I use automake
that in the end runs libtool as:
../../../libtool  --tag=CC   --mode=link gcc -std=gnu99
-fdiagnostics-show-option -g -O2 -maes -mpclmul   -o libintel.la
aes-x86.lo x64_do_rdtsc.o x64_iaesx64.o  -ldl -lpthread

The x64_do_rdtsc.o x64_iaesx64.o are the yasm generated files. libtool
then reports:
*** Warning: Linking the shared library libintel.la against the non-libtool
*** objects  x64_do_rdtsc.o x64_iaesx64.o is not portable!
libtool: link: rm -fr  .libs/libintel.a .libs/libintel.la
libtool: link: ar cru .libs/libintel.a .libs/aes-x86.o
libtool: link: ranlib .libs/libintel.a

and doesn't include the yasm generated files at all! This doesn't
seem correct. I attach a patch that fixes the issue for me
although I don't know whether I really fix the underlying issue.

regards,
Nikos
[patch.txt (text/plain, attachment)]

This bug report was last modified 14 years and 75 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.