Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] problems building x86_64 target
Date: Mon, 11 Jun 2007 17:56:24 +0200	[thread overview]
Message-ID: <20070611155624.GB28991@aon.at> (raw)
In-Reply-To: <20070607101948.GH2853@aon.at>

On Thu, Jun 07, 2007 at 12:19:48PM +0200, Bernhard Fischer wrote:
>On Wed, Jun 06, 2007 at 05:31:25PM -0700, kevint wrote:
>>Hello,
>>
>>Thanks for your tips.  I set --disable-libmudflap in "Additional gcc  
>>options", and that got past the error I first came across, but I also  
>>had to modify a couple things to get it to compile the rest of the way:
>
>I tried this yesterday and yes, it's broken ATM.
>The includes are pretty messed up, could be that the patch in the thread
>with subject "sysroot support in toolchain, use correct pathes" in the
>archives helps there. This needs proper fixing anyway and this patch
>does make it better (didn't try x86_64, though) but since gcc-3.4
>doesn't have sysroot support, it breaks in many funny ways, of course.
>All vaguely recent gcc -- i.e. the 4.x series onward -- do have proper
>sysroot support and work flawlessly.
>
>I'll have a look at it again.

http://uclibc.org/~aldot/buildroot/buildroot.mine.cow.20070611-1730.diff.bz2

This was tested with sysroot support enabled, gcc-4.2.0. I intend to apply
this once i get a chance to test if building gcc-3.4.6 without sysroot works
as expected.

In the meantime you can use this patch to build a working x86_64 rootfs.

HTH,
Bernhard

  reply	other threads:[~2007-06-11 15:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 17:16 [Buildroot] problems building x86_64 target kevint
2007-06-06 17:38 ` Bernhard Fischer
2007-06-06 18:40   ` Bernhard Fischer
2007-06-07  0:31     ` kevint
2007-06-07 10:19       ` Bernhard Fischer
2007-06-11 15:56         ` Bernhard Fischer [this message]
2007-06-11 16:28           ` kevint
2007-06-11 22:08             ` Bernhard Fischer
2007-06-11 23:10               ` kevint

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=20070611155624.GB28991@aon.at \
    --to=rep.dot.nop@gmail.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