From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5486] libglib2 build fails on qsort r test
Date: Fri, 31 Aug 2012 00:08:05 +0000 (UTC) [thread overview]
Message-ID: <20120831000805.3DFD4994DF@busybox.osuosl.org> (raw)
In-Reply-To: <bug-5486-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=5486
--- Comment #1 from twobob <seetwobob@live.co.uk> 2012-08-31 00:08:04 UTC ---
(In reply to comment #0)
> Using CS TC (current or otherwise), 32 bit system. Builroot latest via GIT
>
> libglib2-2.30.2
>
> As a general overview:
> CFLAGS="-fno-stack-protector -O2 -ffast-math -march=armv6j -mtune=arm1136jf-s
> -mfpu=vfp -pipe -$fomit-frame-pointer"
> CXXFLAGS="-fno-stack-protector" CPPFLAGS="-U_FORTIFY_SOURCE"
> HOST=i686-pc-linux
> BUILD=arm-unknown-linux-gnueabi
>
> Whilst:
> >>> libglib2 2.30.2 Building
> Fails with
> CC gtester.o
> CCLD libglib-2.0.la
> CCLD gtester
> ./.libs/libglib-2.0.so: undefined reference to `qsort_r'
> collect2: ld returned 1 exit status
>
> There was some reference (related? maybe?) to an embedded patch for libglib2 re
> another system here: http://patches.openembedded.org/patch/14169/
> Perhaps it is relevant.
>
> This is my first bug report apologies for any elided required info.
> Will be glad to forward any extra required.
>
> Regards.
Just wanted to add that the link doesn't actually point to the fix/patch
itself. it's a monologue about when it should be used. and a patch for when it
would be applied in the other system. Thanks
--
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 prev parent reply other threads:[~2012-08-31 0:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 0:02 [Buildroot] [Bug 5486] New: libglib2 build fails on qsort r test bugzilla at busybox.net
2012-08-31 0:08 ` bugzilla at busybox.net [this message]
2012-08-31 0:23 ` [Buildroot] [Bug 5486] " bugzilla at busybox.net
2012-08-31 0:26 ` bugzilla at busybox.net
2012-08-31 7:42 ` bugzilla at busybox.net
2012-08-31 13:18 ` bugzilla at busybox.net
2012-08-31 14:41 ` bugzilla at busybox.net
2012-08-31 15:07 ` bugzilla at busybox.net
2012-08-31 15:10 ` [Buildroot] [Bug 5486] libglib2 build fails on: py-compile: Missing argument to --destdir bugzilla at busybox.net
2012-08-31 22:04 ` [Buildroot] [Bug 5486] libglib2 build fails on: libs/libglib-2.0.so: undefined reference to `qsort_r' bugzilla at busybox.net
2012-08-31 22:10 ` bugzilla at busybox.net
2012-09-01 13:29 ` bugzilla at busybox.net
2012-09-02 0:42 ` 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=20120831000805.3DFD4994DF@busybox.osuosl.org \
--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.