From: Eial Czerwacki <eial@scalemp.com>
To: buildroot@busybox.net
Subject: [Buildroot] segfault when running a simple c program on env build with buildroot
Date: Sun, 12 Feb 2012 09:14:56 +0200 [thread overview]
Message-ID: <4F3766F0.1070006@scalemp.com> (raw)
In-Reply-To: <20120209165457.2a99305b@skate>
On 02/09/2012 05:54 PM, Thomas Petazzoni wrote:
> Le Thu, 09 Feb 2012 17:16:51 +0200,
> Eial Czerwacki <eial@scalemp.com> a ?crit :
>
>>> What is your hardware platform?
>>>
>>> Thomas
>>
>> any generic Intel/AMD cpu
>
> Sorry this does not exist. Your configuration states i686. If your
> processor is only i486 or i586 compatible, then those segfaults are
> expected since the generated code might use instructions that do not
> exist on your processor.
>
correction, the cpus are any cpus from the last 4-5 years, my cpu is
e6600 for the matter.
all of them are i686
>> I've compiled iasl, dmidecode and biosdecode with same image, you say
>> that I cannot do that?
>> I need the bin linked to uclibc and my desktop doesn't support uclibc
>
> Buildroot generates for you an uClibc cross-compilation toolchain in
> output/host/usr/bin that you can use to cross-compile applications for
> the target platform.
>
> Best regards,
>
> Thomas
that is what I need.
Eial.
next prev parent reply other threads:[~2012-02-12 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 14:48 [Buildroot] segfault when running a simple c program on env build with buildroot Eial Czerwacki
2012-02-09 15:09 ` Thomas Petazzoni
2012-02-09 15:11 ` Thomas Petazzoni
2012-02-09 15:16 ` Eial Czerwacki
2012-02-09 15:54 ` Thomas Petazzoni
2012-02-12 7:14 ` Eial Czerwacki [this message]
2012-02-12 8:25 ` Eial Czerwacki
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=4F3766F0.1070006@scalemp.com \
--to=eial@scalemp.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