From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2395] New: libglib2-2.24.1 and libxml2-2.7.7 on MIPS because is missing -ldl
Date: Wed, 11 Aug 2010 17:00:46 +0000 (UTC) [thread overview]
Message-ID: <bug-2395-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2395
Summary: libglib2-2.24.1 and libxml2-2.7.7 on MIPS because is
missing -ldl
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: sergio at sergiomb.no-ip.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0
with buildroot git version from today .
same config of bug #635 (https://bugs.busybox.net/attachment.cgi?id=2269)
I have to make cd buildroot/output/build/libglib2-2.24.1/
vi gio/Makefile
and add -ldl to LIBS
LIBS = -lintl -ldl
same for gio/tests/Makefile
for libxml2-2.7.7 happens the same.
cd buildroot/output/build/libxml2-2.7.7/
I had to add -ldl to LIBS on
Makefile
doc/examples/Makefile
example/Makefile
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-08-11 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 17:00 bugzilla at busybox.net [this message]
2010-08-11 18:53 ` [Buildroot] [Bug 2395] libglib2-2.24.1 and libxml2-2.7.7 fails build on MIPS because is missing -ldl bugzilla at busybox.net
2010-08-13 14:25 ` bugzilla at busybox.net
2010-08-13 15:06 ` bugzilla at busybox.net
2010-08-16 20:26 ` bugzilla at busybox.net
2010-08-17 17:19 ` bugzilla at busybox.net
2010-08-26 12:00 ` bugzilla at busybox.net
2010-08-30 8:43 ` bugzilla at busybox.net
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=bug-2395-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 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.