From: David Brown <david@westcontrol.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot fails to build shared library for libglib12 on avr32
Date: Tue, 13 Jan 2009 14:29:37 +0100 [thread overview]
Message-ID: <gki4sh$tpl$1@ger.gmane.org> (raw)
Should I be posting this sort of thing here in the mailing list, or
using the bug tracker?
When building for the avr32, libglib12 does not build a shared library
for the target, and therefore fails to build properly. The fix, as far
as I can see, is to patch "ltconfig" so that avr32 builds are treated
like uclibc builds. I based this on an old mailing list post:
http://lists.busybox.net/pipermail/buildroot/2008-February/007030.html
The post refers to issue number 1478 in the bug tracker for busybox, but
I can't find a bug with this number.
Adding the following patch to package/libglib12 fixes the problem:
package/libglib12/libglib-sharedlib-avr32.patch
--- glib/ltconfig
+++ glib/ltconfig
@@ -1982,7 +1982,7 @@
fi
;;
-linux-uclibc*)
+linux-uclibc* | avr32-linux*)
version_type=linux
need_lib_prefix=no
need_version=no
mvh.,
David Brown
next reply other threads:[~2009-01-13 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 13:29 David Brown [this message]
2009-01-15 22:20 ` [Buildroot] Buildroot fails to build shared library for libglib12 on avr32 Ulf Samuelsson
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='gki4sh$tpl$1@ger.gmane.org' \
--to=david@westcontrol.com \
--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