Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Foos <rick@synchromeshcomputing.com>
To: buildroot@busybox.net
Subject: [Buildroot] BASE_TARGETS aren't build
Date: Thu, 26 Jul 2007 02:20:50 -0500	[thread overview]
Message-ID: <001401c7cf55$7f2bb890$6404a8c0@shukson> (raw)
In-Reply-To: 20070725200039.GA26294@firebird.dresden.micronet24.de

GDB in particular is now broken on a clean build, and stops the build. This 
recently happened.

I agree many others have been trying to build w/o a toolchain for some time.

Rick Foos

----- Original Message ----- 
From: "Benjamin Tietz" <benjamin@micronet24.de>
To: <buildroot@uclibc.org>
Sent: Wednesday, July 25, 2007 3:00 PM
Subject: [Buildroot] BASE_TARGETS aren't build


> Hi,
>
> some days ago the building of the toolchain and the crosscompiler was
> moved from TARGETS to BASE_TARGETS, and the second made dependent of the
> first. It looked nice, but at least for me, it doesn't work.
>
> Getting a virgin buildroot building all the packages (and the toolchain)
> doesn't take this dependency in account and starts to compile packages
> for the target. Without an working gcc this may be difficult...
>
> There were a rule, some time ago - never break the build - where is it
> gone. Some time ago the buildroot built, even for avr32, without to much
> problems. There going discussions on about distributional packages and 
> BSPs.
> But as long as the toolchain doesn't built, all these gimmicks aren't
> usable.
>
> By the way that problem isn't the only thing broken at the moment; I
> fixed it by now by reverting the patch and letting the toolchain compile
> as usual targets.
>
> regards
>
> Benjamin
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
> 

  reply	other threads:[~2007-07-26  7:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 20:00 [Buildroot] BASE_TARGETS aren't build Benjamin Tietz
2007-07-26  7:20 ` Rick Foos [this message]
2007-07-27 14:53 ` Bernhard Fischer

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='001401c7cf55$7f2bb890$6404a8c0@shukson' \
    --to=rick@synchromeshcomputing.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