From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problems with uClicbc and libc.so.6
Date: Thu, 9 Oct 2014 15:07:27 +0200 [thread overview]
Message-ID: <20141009150727.441ae173@free-electrons.com> (raw)
In-Reply-To: <CA+TH9VnQmn=7qX9Ao2qST1z3Sr8uVsFBB5xe5ASrNCLBdo9GsQ@mail.gmail.com>
Dear Angelo Compagnucci,
On Thu, 9 Oct 2014 14:58:55 +0200, Angelo Compagnucci wrote:
> > If something depends on libc.so.6, it means it was built against glibc,
> > and cannot work against uClibc. So either it's something built from
> > source, and you should rebuilt it with the uClibc toolchain. Or it's
> > something available as a pre-built binary for which you don't have the
> > source, in which case you have no other choice than using glibc.
>
> I just rebuilt everything from scratch using the latest buildroot git
> and the problem persists.
> The package I'm using is more or less this one:
>
> http://patchwork.ozlabs.org/patch/392957/, I've only added a small
> patch to make compile cleanly with uClibc.
>
> diff -purN mono-native-3.8.0.orig/libgc/include/gc.h
> mono-native-3.8.0/libgc/include/gc.h
> --- mono-native-3.8.0.orig/libgc/include/gc.h 2014-10-07
> 15:00:21.259466731 +0200
> +++ mono-native-3.8.0/libgc/include/gc.h 2014-10-07 15:05:25.560975681 +0200
> @@ -500,7 +500,7 @@ GC_API GC_PTR GC_malloc_atomic_ignore_of
> #ifdef __linux__
> # include <features.h>
> # if (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 1 || __GLIBC__ > 2) \
> - && !defined(__ia64__)
> + && !defined(__ia64__) && !defined(__UCLIBC__)
> # ifndef GC_HAVE_BUILTIN_BACKTRACE
> # define GC_HAVE_BUILTIN_BACKTRACE
> # endif
>
> This package is based on my previous work that I used regularly on
> older buildroot versions. The only thing that changed is the bump to
> mono version 3.8.0.
>
> > I am a bit surprised that it works. It is in any case completely wrong,
> > and there is absolutely no guarantee that uClibc and glibc are ABI
> > compatible.
>
> Based on my limited knowledge of Buildroot internals, it should work
> because the only toolchain I selected is the one built by buildroot
> with uClibc 0.9.33.x. Honestly I think that something in between mono
> cross compilation links erroneously to libc instead to uClibc so the
> error is explained.
>
> I can disable mono when toolchain is uClibc based, but I really want
> to narrow down and resolve the problem.
Can you push a branch somewhere with all the needed patches + a minimal
Buildroot configuration that exhibits the problem as well as the
instructions to test this and reproduce the issue you're seeing?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-09 13:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 10:35 [Buildroot] Problems with uClicbc and libc.so.6 Angelo Compagnucci
2014-10-09 11:54 ` Thomas Petazzoni
2014-10-09 12:58 ` Angelo Compagnucci
2014-10-09 13:07 ` Thomas Petazzoni [this message]
2014-10-09 15:58 ` Angelo Compagnucci
2014-10-09 16:02 ` Thomas Petazzoni
2014-10-09 16:40 ` Angelo Compagnucci
2014-10-09 20:20 ` Thomas Petazzoni
2014-10-10 7:46 ` Angelo Compagnucci
2014-10-10 10:34 ` Thomas Petazzoni
2014-10-10 10:45 ` Angelo Compagnucci
2014-10-10 11:06 ` Thomas Petazzoni
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=20141009150727.441ae173@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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