From: Sasha Sirotkin <buildroot@browserseal.com>
To: buildroot@busybox.net
Subject: [Buildroot] init segfaults when compiled with glibc
Date: Wed, 31 Mar 2010 21:28:29 +0300 [thread overview]
Message-ID: <4BB3944D.2080301@browserseal.com> (raw)
In-Reply-To: <87mxxo8ipp.fsf@macbook.be.48ers.dk>
Peter Korsgaard wrote:
>>>>>> "Alexander" == Alexander (Sasha) Sirotkin <buildroot@browserseal.com> writes:
>>>>>>
>
> Alexander> I did not manage to compile crosstoll-ng with eglibc yet. It
> Alexander> looks like eglibc support is broken in crosstool-ng and
> Alexander> glibc support is broken in buildroot.
>
> uClibc? We don't have glibc support (except for external toolchains), so
> it cannot really be broken ;)
>
>
Well... it is broken in a sense that buildroot does not work with an
external toolchain based on glibc. Please see above.
next prev parent reply other threads:[~2010-03-31 18:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 14:26 [Buildroot] init segfaults when compiled with glibc Sasha Sirotkin
2010-03-30 16:58 ` Yann E. MORIN
2010-03-30 22:20 ` Eric BENARD
2010-03-31 14:18 ` Alexander Sirotkin
2010-03-31 14:37 ` Javier Viguera
2010-03-31 15:48 ` Alexander Sirotkin
2010-03-31 18:11 ` Peter Korsgaard
2010-03-31 18:28 ` Sasha Sirotkin [this message]
2010-03-31 18:58 ` H Hartley Sweeten
2010-03-31 19:02 ` Sasha Sirotkin
2010-03-31 19:16 ` Thomas Petazzoni
2010-03-31 20:21 ` Alexander Sirotkin
2010-04-01 7:48 ` Alexander Sirotkin
-- strict thread matches above, loose matches on Subject: below --
2010-03-31 10:47 Sasha Sirotkin
2010-03-31 18:52 ` Thomas Petazzoni
2010-03-31 20:05 ` Alexander Sirotkin
2010-03-30 20:03 Sasha Sirotkin
2010-03-30 20:34 ` Thomas Petazzoni
2010-03-30 12:27 Sasha Sirotkin
2010-03-30 13:20 ` Yann E. MORIN
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=4BB3944D.2080301@browserseal.com \
--to=buildroot@browserseal.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