From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] init segfaults when compiled with glibc
Date: Tue, 30 Mar 2010 22:34:48 +0200 [thread overview]
Message-ID: <20100330223448.0dd60fa9@surf> (raw)
In-Reply-To: <4BB2592B.4080502@browserseal.com>
Hi Sasha,
On Tue, 30 Mar 2010 23:03:55 +0300
Sasha Sirotkin <buildroot@browserseal.com> wrote:
> It looks like glibc does not work at all with buildroot right now.
> Should I open a bug ticket or something?
Unfortunately, without more details, a bug report would be fairly
useless. Can you send your Buildroot .config and kernel .config so that
I can try to reproduce your problem on my AT91 systems ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-03-30 20:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 20:03 [Buildroot] init segfaults when compiled with glibc Sasha Sirotkin
2010-03-30 20:34 ` Thomas Petazzoni [this message]
-- 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 14:26 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
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
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=20100330223448.0dd60fa9@surf \
--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 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.