Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] divine: fix divine-config
Date: Tue, 08 Jan 2013 08:48:18 +0100	[thread overview]
Message-ID: <50EBCF42.3000505@mind.be> (raw)
In-Reply-To: <50EB4DAD.6040409@petroprogram.com>

On 07/01/13 23:35, Stefan Fr?berg wrote:
> Hi Arnout
>
> 8.1.2013 0:17, Arnout Vandecappelle kirjoitti:
>> On 06/01/13 19:12, Stefan Fr?berg wrote:
[snip]
>>> ui/libui.a codecs/libcodec.a wiretap/.libs/libwiretap.a
>>> epan/.libs/libwireshark.a -lgnutls -L/usr/lib
>>                                       ^^^^^^^^^^
>>   Here's your culprit.
>>
>>   Probably one of the .la files incorrectly adds /usr/lib.
>>
>>   Question is why libtool adds it, of course...
>>
>
> Bug in libtool ?
> I tried checking all my $(STAGING_DIR)/usr/lib/*.la files but so far
> everything seems fine...

  I expect it will be one of the *.la files in wireshark itself. Or it 
could be one of the -lfoo link arguments - IIRC, libtool hard-codes 
searching in /usr/lib for libraries.

  Looking a bit more in detail, I see that autoconf's AC_PROG_LIBTOOL 
expands into a hard-coded
sys_lib_dlsearch_path_spec="/lib /usr/lib \$lt_ld_extra"

(sys_lib_search_path_spec is computed based on the compiler's search 
path.) So we actually risk running into this problem for any 
libtool-based package... Maybe we should globally patch the configure 
scripts to make sys_lib_dlsearch_path_spec empty.

  But anyway, Stefan, for wireshark you should try to find out which host 
library is found by configure. Because making sys_lib_dlsearch_path_spec 
empty would just change the error into a slightly better 'cannot find -lfoo'.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-01-08  7:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 22:09 [Buildroot] [PATCH] divine: fix divine-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] giblib: fix giblib-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] imlib2: fix imlib2-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] libgcrypt: fix libgcrypt-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] imagemagick: fix Magick[++|Core|Wand]-config Stefan Fröberg
2013-01-04 21:45   ` Peter Korsgaard
2013-01-03 22:09 ` [Buildroot] [PATCH] neon: fix neon-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] libnspr: fix nspr-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] xlib_libXft: fix xft-config Stefan Fröberg
2013-01-04 23:30   ` Peter Korsgaard
2013-01-05 13:33     ` Stefan Fröberg
2013-01-04 11:41 ` [Buildroot] [PATCH] divine: fix divine-config Gustavo Zacarias
2013-01-04 14:17   ` Samuel Martin
2013-01-04 14:29     ` Gustavo Zacarias
2013-01-04 14:56       ` Stefan Fröberg
2013-01-04 15:00         ` Gustavo Zacarias
2013-01-06  5:41         ` Baruch Siach
2013-01-06  8:27           ` Samuel Martin
2013-01-06  8:34             ` Baruch Siach
2013-01-06 12:39               ` Thomas Petazzoni
2013-01-06 14:15           ` Stefan Fröberg
2013-01-06 18:12           ` Stefan Fröberg
2013-01-07 22:17             ` Arnout Vandecappelle
2013-01-07 22:35               ` Stefan Fröberg
2013-01-08  7:48                 ` Arnout Vandecappelle [this message]
2013-01-08  8:10                   ` Thomas Petazzoni
2013-01-08  8:24                     ` Arnout Vandecappelle
2013-01-04 16:29     ` Thomas Petazzoni
2013-01-04 16:31   ` Thomas Petazzoni
2013-01-04 17:10     ` Gustavo Zacarias
2013-01-04 17:13       ` Stefan Fröberg
2013-01-04 21:49 ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50EBCF42.3000505@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox