Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot:packagetarget/device/Atmel
Date: Thu, 26 Jul 2007 08:03:36 +0200	[thread overview]
Message-ID: <00a301c7cf52$61ac2cd0$dcc4af0a@atmel.com> (raw)
In-Reply-To: 1185428949.31437.4.camel@localhost.localdomain

----- Original Message ----- 
From: "Hans-Christian Egtvedt" <hcegtvedt@atmel.com>
To: "Ulf Samuelsson" <ulf@atmel.com>
Cc: "Steven J. Hill" <sjhill@realitydiluted.com>; <buildroot@uclibc.org>
Sent: Thursday, July 26, 2007 7:49 AM
Subject: Re: [Buildroot] svn commit: trunk/buildroot:packagetarget/device/Atmel


> 
> On Mon, 2007-07-23 at 00:49 +0200, Ulf Samuelsson wrote:
>> > ulf at uclibc.org wrote:
> 
> <cut adding ATMEL_MIRROR and revert>
> 
>> While it is used for target/device/Atmel files, it is also needed
>> to download binutils/gcc/gdb tarballs for AVR32 architecture support.
>> If it is defined in target/device/Atmel, then it is not defined during
>> the toolchain build. causing this to fail.
>> 
>> The alternative is to submit a 7-10 MB patch+ for the buildroot tree
>> with all the AVR32 architecture patches, which I thought was a bad idea.
> 
> I hope to get these patches smaller, many of them contain 90% hacking on
> the automake system.
> 
> Right now they are roughly 8 MB for all the tools (gcc, binutils, gdb,
> strace, uClibc and kernel). But this is in plain text, and they compress
> well.
> 
> <cut location discussion>
> 
> -- 
> With kind regards,
> 
> Hans-Christian Egtvedt, siv.ing. (M.Sc.)
> Applications Engineer - AVR32 System Solutions - Atmel Norway
> 


I think that until the AVR32 support is fully integrated in the GCC, it is probably 
just as well, downloading prepatched source instead of running autotool,
unless you can make sure that *any* version of autotools will work.

We can't expect a user to have a certain version of autotool, unless we 
download and build it as part of buildroot.

Best Regards
Ulf Samuelsson

  parent reply	other threads:[~2007-07-26  6:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22 17:17 [Buildroot] svn commit: trunk/buildroot: package target/device/Atmel ulf at uclibc.org
2007-07-22 20:00 ` Steven J. Hill
2007-07-22 22:49   ` [Buildroot] svn commit: trunk/buildroot: packagetarget/device/Atmel Ulf Samuelsson
2007-07-23  2:55     ` Steven J. Hill
2007-07-23  6:25       ` Ulf Samuelsson
     [not found]     ` <1185428949.31437.4.camel@localhost.localdomain>
2007-07-26  6:03       ` Ulf Samuelsson [this message]
2007-07-26  7:30         ` [Buildroot] svn commit: trunk/buildroot:packagetarget/device/Atmel Hans-Christian Egtvedt
     [not found]         ` <1185434977.31437.50.camel@localhost.localdomain>
2007-07-26 16:55           ` Ulf Samuelsson
2007-07-27  6:07             ` Hans-Christian Egtvedt
2007-07-27  8:48               ` Ulf Samuelsson
2007-07-27 14:11               ` Hans-Christian Egtvedt
2007-07-26  7:01     ` [Buildroot] svn commit: trunk/buildroot: packagetarget/device/Atmel Hans-Christian Egtvedt
  -- strict thread matches above, loose matches on Subject: below --
2007-07-23  9:40 Ulf Samuelsson

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='00a301c7cf52$61ac2cd0$dcc4af0a@atmel.com' \
    --to=ulf@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