Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Moore <scott.moore@sri.com>
To: buildroot@busybox.net
Subject: [Buildroot] Known good x86-64 host/target configuration with dev tools?
Date: Tue, 07 Aug 2012 11:13:10 -0700	[thread overview]
Message-ID: <50215AB6.3050800@sri.com> (raw)

Hi,

I've been trying for some time to build a chroot jail for compiling code 
against uclibc on a x86_64 platform without worrying about contamination 
from the system glibc, etc. To do this, I've been trying to use 
buildroot with development files on the target and gcc/make/etc packages 
enabled. I keep running into problems with the resulting target 
toolchain, though. With NPTL support on, all executables compiled by my 
target gcc segfault. With linuxthreads instead, I still encounter what 
appear to be mis-compiles (though could be bugs in the code I'm compiling).

Since I'm not confident in my configuration, I was wondering if anyone 
has a known good buildroot/uClibc configuration that targets x86_64 with 
a target toolchain with C++ support.

Thanks,
Scott

                 reply	other threads:[~2012-08-07 18:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=50215AB6.3050800@sri.com \
    --to=scott.moore@sri.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