From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-02-25
Date: Thu, 26 Feb 2015 20:39:31 +0200 [thread overview]
Message-ID: <20150226183931.GK2402@tarshish> (raw)
In-Reply-To: <20150226073014.150E51017F6@stock.ovh.net>
Hi Thomas, list,
On Thu, Feb 26, 2015 at 08:30:13AM +0100, Thomas Petazzoni wrote:
> x86_64 | make-4.1 | NOK | http://autobuild.buildroot.net/results/b80a34a602b1241bc03cd43df1a269389d50e75c/
Nice.
So we package different versions of the same library under different names.
The library is the Boehm-Demers-Weiser garbage collector that we carry under
the names bdwgc (7.2f), and libgc (7.4.0). The following build order seems to
triggers the error:
bdwgc (guile dependency)
guile
libgc
make
guile links with bdwgc as a mandatory dependency. make-4.1 configure script
finds guile and pulls -lguile-2.0 and -lgc to its link command. But libgc
builds before make, thus overwriting bdwgc. When make attempts to link with
libgc it fails because of missing getcontext, a problem that is fixed in bdwgc
by a local patch.
I have verified that building guile, libgc, and make, in that order,
reproduced this build failure.
I suggest to just remove libgc in master, event though it was added first,
because no other package depend on it.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-02-26 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-02-25 Thomas Petazzoni
2015-02-26 9:30 ` Alex Suykov
2015-02-26 18:39 ` Baruch Siach [this message]
2015-02-26 22:51 ` Peter Korsgaard
2015-02-27 5:50 ` Baruch Siach
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=20150226183931.GK2402@tarshish \
--to=baruch@tkos.co.il \
--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.