From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] add hotplug2 package
Date: Tue, 31 Mar 2009 18:14:50 -0400 [thread overview]
Message-ID: <20090331221450.GA31451@denix.org> (raw)
In-Reply-To: <1238511677.7128.86.camel@alap>
On Tue, Mar 31, 2009 at 09:01:17AM -0600, Angus Ainslie wrote:
> > > +LDFLAGS += "-lglibc"
> >
> > I don't think that actually works, and if it did, uclibc would break
>
> Without that I get undefined refeences
>
> loader.c:(.text+0x14): undefined reference to `dlclose'
> workers/loader.o: In function `worker_load':
> loader.c:(.text+0x44): undefined reference to `dlopen'
> loader.c:(.text+0x5c): undefined reference to `dlsym'
> loader.c:(.text+0x84): undefined reference to `dlerror'
>
> > > +do_configure () {
> > > +}
> >
> > missing colon between the braces. But more importantly: why inherit
> > autotools when you're not going to run configure?
>
> I was under the mistaken impression that autotools need to be included
> to get do_compile() and do_install(). It seems those are the defaults.
>
> There is a deeper problem that without the inherit autotools then the
> LDFLAGS above fails to find glibc. Is there something missing in the
> default case ?
Wow, I'm surprised "-lglibc" above even worked for you:
$ find rootfs -name 'libglibc*'
$
Those undefined references above are provided by libdl.so, which needs:
LDFLAGS += " -ldl"
And no need for autotools.
--
Denys
next prev parent reply other threads:[~2009-03-31 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 22:40 [PATCH] add hotplug2 package Angus Ainslie
2009-03-31 6:53 ` Koen Kooi
2009-03-31 15:01 ` Angus Ainslie
2009-03-31 22:14 ` Denys Dmytriyenko [this message]
2009-04-01 13:08 ` Angus Ainslie
2009-04-01 13:41 ` Koen Kooi
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=20090331221450.GA31451@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@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.