All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] gnutls: link against 'dl' library
Date: Thu, 2 Jun 2011 08:31:30 +0200	[thread overview]
Message-ID: <20110602063130.GG3281@jama.jama.net> (raw)
In-Reply-To: <4DE6BAE6.3040406@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3307 bytes --]

On Wed, Jun 01, 2011 at 03:19:18PM -0700, Saul Wold wrote:
> On 06/01/2011 02:52 PM, Martin Jansa wrote:
> > On Wed, Jun 01, 2011 at 02:43:53PM -0700, Saul Wold wrote:
> >> On 06/01/2011 02:00 PM, Otavio Salvador wrote:
> >>> On Wed, Jun 1, 2011 at 20:53, Phil Blundell<pb@pbcl.net>   wrote:
> >>>> On Wed, 2011-06-01 at 20:39 +0000, Otavio Salvador wrote:
> >>>>> Are you able to reproduce it?
> >>>>
> >>>> No, it works fine for me.  I get:
> >>>>
> >>>> checking how to link with libpthread... -lpthread
> >>>> checking for libdl... yes
> >>>> checking how to link with libdl... -ldl
> >>>> checking whether we are using the GNU C++ compiler... yes
> >>>>
> >>>> This is with the current head of oe-core on qemuarm.
> >>>
> >>> I am building for i586 but I doubt it is related.
> >>>
> >>> I get:
> >>>
> >>> checking for libpthread... yes
> >>> checking how to link with libpthread... /usr/lib/libpthread.so
> >>> checking for libdl... no
> >>> checking whether we are using the GNU C++ compiler... yes
> >>>
> >> I also built for x86 and beagle, both have libdl, can you check that you
> >> do not have some kind of site configuration that is overriding, also
> >> maybe post your log from .../gnutls-2.12.5/lib/config.log
> >
> > here it tries to link against host libdl
> >
> > configure:26050: checking for libdl
> > configure:26069: arm-oe-linux-gnueabi-gcc -march=armv4t -mtune=arm920t
> > --sysroot=/OE/shr-core/tmp/sysroots/om-gta02 -o conftest -O2 -pipe -g
> > -feliminate-unused-debug-types
> > -I/OE/shr-core/tmp/sysroots/om-gta02/usr/include -Wl,-O1
> > -Wl,--as-needed conftest.c  /usr/lib/libdl.so>&5
> > /usr/lib/libdl.so: file not recognized: File format not recognized
> > collect2: ld returned 1 exit status
> >
> Well that's interesting, since I see it linking using -ldl, there must 
> be some other setting that's affecting this, I have been looking in 
> gnutls to see if I can find something else that sets libdl.so vs -ldl,
> I have not found it.
> 
> configure:26075: i586-poky-linux-gcc -march=i586 
> --sysroot=/builds/world/tmp/sysroots/qemux86 -o conftest -O2 -pipe -g 
> -feliminate-unused-debug-types 
> -I/builds/world/tmp/sysroots/qemux86/usr/include -Wl,-O1 
> -Wl,--as-needed conftest.c  -ldl >&5
> configure:26075: $? = 0
> configure:26085: result: yes
> configure:26092: checking how to link with libdl
> configure:26094: result: -ldl

what do you have in configlog for LIBDL?

here it's all empty
LIBDL=''
LIBDL_PREFIX=''
LTLIBDL=''

if I add 
+             --with-libdl-prefix=${STAGING_DIR_HOST}${prefix} \
+             --with-libpthread-prefix=${STAGING_DIR_HOST}${prefix} \
to EXTRA_OE_CONF (we already have couple of --with-*-prefix there) it's
found correctly (and this is at least better workarround then forcing
-ldl directly to LDFLAGS):
LIBDL='/OE/shr-core/tmp/sysroots/om-gta02/usr/lib/libdl.so'
LIBDL_PREFIX='/OE/shr-core/tmp/sysroots/om-gta02/usr'
LTLIBDL='-L/OE/shr-core/tmp/sysroots/om-gta02/usr/lib -ldl'

same problem is with libpthread..

maybe their m4/lib-link.m4 does something wrong in
AC_DEFUN([AC_LIB_HAVE_LINKFLAGS],
[
  AC_REQUIRE([AC_LIB_PREPARE_PREFIX])
  AC_REQUIRE([AC_LIB_RPATH])

Regards,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

  reply	other threads:[~2011-06-02  6:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 20:09 [PATCH 0/3] Patches pending on O.S. Systems tree Otavio Salvador
2011-06-01 20:09 ` [PATCH 1/3] busybox: enable mdev by default Otavio Salvador
2011-06-01 20:37   ` Phil Blundell
2011-06-01 20:40     ` Otavio Salvador
2011-06-02 16:37       ` Richard Purdie
2011-06-02 16:40         ` Otavio Salvador
2011-06-03  1:06         ` Khem Raj
2011-06-03  6:37           ` Koen Kooi
2011-06-03  8:24             ` Richard Purdie
2011-06-03  8:59               ` Koen Kooi
2011-06-03  9:50                 ` Richard Purdie
2011-06-03 10:42                   ` Koen Kooi
2011-06-03  9:57           ` Phil Blundell
2011-06-01 20:09 ` [PATCH 2/3] qmake_base.bbclass: fix lrelease/lupdate binary names Otavio Salvador
2011-06-02 16:51   ` Paul Eggleton
2011-06-02 17:27     ` Richard Purdie
2011-06-01 20:09 ` [PATCH 3/3] gnutls: link against 'dl' library Otavio Salvador
2011-06-01 20:33   ` Phil Blundell
2011-06-01 20:39     ` Otavio Salvador
2011-06-01 20:53       ` Phil Blundell
2011-06-01 21:00         ` Otavio Salvador
2011-06-01 21:43           ` Saul Wold
2011-06-01 21:52             ` Martin Jansa
2011-06-01 22:19               ` Saul Wold
2011-06-02  6:31                 ` Martin Jansa [this message]
2011-06-02  9:29                   ` Koen Kooi
2011-06-02  9:38                   ` Richard Purdie
2011-06-02 11:00                     ` [PATCH] gnutls: add --with-libdl-prefix and --with-libpthread-prefix Martin Jansa
2011-06-02 13:53                       ` Richard Purdie

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=20110602063130.GG3281@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.