All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5486] libglib2 build fails on: libs/libglib-2.0.so: undefined reference to `qsort_r'
Date: Sun,  2 Sep 2012 00:42:30 +0000 (UTC)	[thread overview]
Message-ID: <20120902004230.6DC8E994F7@busybox.osuosl.org> (raw)
In-Reply-To: <bug-5486-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=5486

--- Comment #10 from twobob <seetwobob@live.co.uk> 2012-09-02 00:42:29 UTC ---
(In reply to comment #9)
> In essence, this doesn't happen using the Buildroot installed Code Sourcery
> Toolchains.
> 
> For my use case I was attempting to utitlise a pre-installed chain.
> It was possibly too old a version.
> 
> Using the 2011 TC fixes this. So I will set it as a non issue and possibly add
> a note when I figure out the oldest CS TC that *will* build this without error.
> 
> (I run all this on a 3rd gen kindle, no really)
> Thanks for all your help.
> 
> If I find something *actually* useful to contribute I will.
> Regards.

Okay as promised.   

CCLD   libglib-2.0.la
  CCLD   gtester
./.libs/libglib-2.0.so: undefined reference to `qsort_r'

First exhibits in Toolchains older than 

rm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

From here:

http://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/

so perhaps a "min required version" might properly reflect that.

2008q3 onward all build as expected.

-- 
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.

      parent reply	other threads:[~2012-09-02  0:42 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 ` [Buildroot] [Bug 5486] " bugzilla at busybox.net
2012-08-31  0:23 ` 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 [this message]

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=20120902004230.6DC8E994F7@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.