From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: buildroot@busybox.net
Subject: [Buildroot] undefined reference to dlsym dlopen dlclose
Date: Mon, 02 Aug 2010 13:19:03 +0100 [thread overview]
Message-ID: <1280751543.5624.3.camel@segulix> (raw)
Hi, can anyone help me on this ?
As you may know, from this ML, I am trying compiling some apps to mipsel
arch , and now with git version I am stuck on this error.
../gmodule/.libs/libgmodule-2.0.so: undefined reference to `dlsym'
../gmodule/.libs/libgmodule-2.0.so: undefined reference to `dlopen'
../gmodule/.libs/libgmodule-2.0.so: undefined reference to `dlclose'
collect2: ld returned 1 exit status
make[5]: *** [gio-querymodules] Error 1
make[5]: Leaving directory
`/home/sergio/hardware/moviecube/buildroot/output/build/libglib2-2.24.1/gio'
Any feedback is appreciated
--
S?rgio M. B.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3293 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100802/588f27e5/attachment.bin>
next reply other threads:[~2010-08-02 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 12:19 Sergio Monteiro Basto [this message]
2010-08-02 18:38 ` [Buildroot] undefined reference to dlsym dlopen dlclose Sergio Monteiro Basto
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=1280751543.5624.3.camel@segulix \
--to=sergio@sergiomb.no-ip.org \
--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