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 qsort r test
Date: Fri, 31 Aug 2012 15:07:54 +0000 (UTC)	[thread overview]
Message-ID: <20120831150754.6AA36994DA@busybox.osuosl.org> (raw)
In-Reply-To: <bug-5486-163@https.bugs.busybox.net/>

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

--- Comment #7 from twobob <seetwobob@live.co.uk> 2012-08-31 15:07:54 UTC ---
(In reply to comment #6)
> Well, yes, the fix that Peter committed specifically addresses the uCLibC case.
> If your external toolchain doesn't provide qsort_r, then your build will still
> fail.
> 
> I am not sure if this can be fixed properly in buildroot as we can't know all
> details about any possible external toolchain. But you can work around this by
> adding "glib_cv_have_qsort_r=no" to LIBGLIB2_CONF_ENV in your tree.

Okay some progress.

As I said I am unsure why but defaulting the values via your method. Now read
up on the process so I understand that should have defaulted the value to yes -
which *is* the case for the TC.

so to *get further* I simply elided the test as per the patch I referenced
above which got me one step farther; past the qsort_r error with it correctly
identified to the positive.

Which led to a fail testing the stack growth. I razed everything to the ground
and started again. applied the qsort_r.patch I referenced and this time I get.

tests'
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gobject/tests'
make[4]: Leaving directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gobject/tests'
make[3]: Leaving directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gobject'
make[2]: Leaving directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gobject'
Making install in gio
make[2]: Entering directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gio'
/usr/bin/make  install-recursive
make[3]: Entering directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gio'
Making install in gdbus-2.0/codegen
make[4]: Entering directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gio/gdbus-2.0/codegen'
make[5]: Entering directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gio/gdbus-2.0/codegen'
 /bin/mkdir -p '/home/simon/GIT/buildroot/output/host/usr/bin'
 /bin/mkdir -p
'/home/simon/GIT/buildroot/output/host/usr/lib/gdbus-2.0/codegen'
 /usr/bin/install -c gdbus-codegen
'/home/simon/GIT/buildroot/output/host/usr/bin'
 /usr/bin/install -c -m 644 __init__.py codegen.py codegen_main.py
codegen_docbook.py config.py dbustypes.py parser.py utils.py
'/home/simon/GIT/buildroot/output/host/usr/lib/gdbus-2.0/codegen'
../../../py-compile: Missing argument to --destdir.
make[5]: *** [install-codegenPYTHON] Error 1
make[5]: Leaving directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gio/gdbus-2.0/codegen'
make[4]: *** [install-am] Error 2
make[4]: Leaving directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gio/gdbus-2.0/codegen'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gio'
make[2]: *** [install] Error 2
make[2]: Leaving directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/gio'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2'
make: ***
[/home/simon/GIT/buildroot/output/build/host-libglib2-2.30.2/.stamp_host_installed]
Error 2

Is this related to the other python patch - and should I change the title of
the bug report? Attempting to become more useful.

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

  parent reply	other threads:[~2012-08-31 15:07 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 [this message]
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=20120831150754.6AA36994DA@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.