Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1:avr32_patches_break_x86
Date: Tue, 25 Mar 2008 23:58:00 +0100	[thread overview]
Message-ID: <035001c88ece$f13e7ab0$040514ac@atmel.com> (raw)
In-Reply-To: d6cda7730803210833s3cdce637m8b701f53dad302b@mail.gmail.com


> It was a source download, I suspect the behavior might still be in
> there, I haven't tried yet. I was focusing on figuring out in which
> revision things got broken... unfortunally it takes over an hour to
> try each revision. It was a download from the same repository as the
> Atmel's ARM stuff, so, I guess it's now at www.at91.com ftp

You do not need to worry about where the external sources are located.
They are relative to $(BR2_ATMEL_MIRROR)
and you can configure to use the prepatched toolchain inside buildroot 
using make menuconfig

The Config.in for the prepatched toolchain is in "target/device".
Any patches for the prepatched toolchain will be in a subdirectory
of "target/device/Atmel".

Best Regards
Ulf Samuelsson 

  parent reply	other threads:[~2008-03-25 22:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 11:21 [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86 ninevoltz at uclibc.org
2008-03-21 11:39 ` Peter Korsgaard
2008-03-21 11:55   ` John Voltz
2008-03-21 15:14     ` Thiago A. Corrêa
2008-03-21 15:24       ` John Voltz
2008-03-21 15:33         ` Thiago A. Corrêa
2008-03-21 15:44           ` John Voltz
     [not found]             ` <47E3D9E4.6000901@apss.it>
2008-03-21 16:31               ` John Voltz
2008-03-22  2:11             ` Thiago A. Corrêa
2008-03-25 22:58           ` Ulf Samuelsson [this message]
2008-03-21 17:21       ` Nigel Kukard
2008-03-21 17:23         ` John Voltz
2008-03-21 17:29           ` John Voltz
2008-03-21 17:32             ` Nigel Kukard

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='035001c88ece$f13e7ab0$040514ac@atmel.com' \
    --to=ulf.samuelsson@atmel.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