Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 09 Feb 2012 17:16:51 +0200	[thread overview]
Message-ID: <4F33E363.5040107@scalemp.com> (raw)
In-Reply-To: <20120209161150.36d6c6d6@skate>

On 02/09/2012 05:09 PM, Thomas Petazzoni wrote:

> Le Thu, 09 Feb 2012 16:48:30 +0200,
> Eial Czerwacki <eial@scalemp.com> a ?crit :
>
>> my buildroot config is attached and the version in use a snapshot from
>> the date 10/9/2011.
>
> What is your hardware platform?
>
> Thomas

any generic Intel/AMD cpu

On 02/09/2012 05:11 PM, Thomas Petazzoni wrote:

> Le Thu, 09 Feb 2012 16:48:30 +0200,
> Eial Czerwacki <eial@scalemp.com> a ?crit :
> 
>> sh-4.1# gcc -o a test.c
> 
> You're using the native gcc on the target, while Buildroot is mostly
> designed for cross-compilation. Our native gcc on the target mechanism
> isn't used/tested a lot, so I would really recommend using the
> cross-compiler on the build machine to build your applications.
> 
> Thomas


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

Thanks,

Eial.

  reply	other threads:[~2012-02-09 15:16 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 [this message]
2012-02-09 15:54     ` Thomas Petazzoni
2012-02-12  7:14       ` Eial Czerwacki
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=4F33E363.5040107@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