Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: don <don_reid@comcast.net>
To: buildroot@busybox.net
Subject: [Buildroot] Libtool error with AVR32
Date: Fri, 28 Sep 2007 09:09:19 -0700	[thread overview]
Message-ID: <20070928160919.GA10853@reid1.localdomain> (raw)
In-Reply-To: <20070927223420.GG20951@aon.at>

On Fri, Sep 28, 2007 at 12:34:20AM +0200, Bernhard Fischer wrote:
> On Thu, Sep 27, 2007 at 03:19:19PM -0700, don wrote:
> >On Thu, Sep 27, 2007 at 10:53:58PM +0200, Ulf Samuelsson wrote:
> >> tor 2007-09-27 klockan 11:17 -0700 skrev don:
> >> > I tried to use the latest AVR32 release from ATmel and got an error.
> >> > Is there somewhere else to post that other than this list?
> >> > 
> >> > The error is in build_avr32_nofpu/libdaemon-0.12 and is:
> 
> >I did not select any packages, just copied the ntgw100_defconfig to
> >.config.
> 
> Ulf, can you point me to a known good revision (of buildroot) that built
> that ntgw100 successfully, please? Modulo libdaemon, or other such
> packages. This would help alot to pinpoint any possible problems.
> 
> Don, I'm still under the impression that you're using something
> provided by atmel and not http://buildroot.uclibc.org/
> This is not the appropriate place for the "latest AVR32 release from
> ATmel" but for buildroot.

I'm using an archive of buildroot that Atmel provides on their website.
I have tried to use the "current" svn buildroot many many times over
months, and it has never worked.  From the list I can see that buildroot
is highly unstable.

I had hoped that Atmel had a frozen version that works.  I'm sure it
does under some conditions.  

In this case I suspect that my up to date Gentoo host has a new version of
autoconf that is doing some new check.  I thought you might want to know
about this as it will probably come up again.

Have you considered creating buildroot releases, which are frozen
excerpt for simple bug fixes?  It seems that the rate of new "features"
is such that the trunk version is in constant flux.

Thank you
Don

  parent reply	other threads:[~2007-09-28 16:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 18:17 [Buildroot] Libtool error with AVR32 don
2007-09-27 20:53 ` Ulf Samuelsson
2007-09-27 22:19   ` don
2007-09-27 22:34     ` Bernhard Fischer
2007-09-27 23:42       ` Ulf Samuelsson
2007-09-28 16:09       ` don [this message]
2007-09-28 16:38         ` Ulf Samuelsson
2007-09-28 18:34           ` don
2007-09-28 16:51         ` Bernhard Fischer
2007-09-28 19:06           ` Ulf Samuelsson
2007-09-28 19:42           ` Ivan Kuten
2007-09-28 19:17             ` Thiago A. Corrêa
2007-09-28 19:29               ` Bernhard Fischer
  -- strict thread matches above, loose matches on Subject: below --
2007-10-14 20:09 don
2007-10-14 23:34 ` Ivan Kuten
2007-10-15  3:47   ` don

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=20070928160919.GA10853@reid1.localdomain \
    --to=don_reid@comcast.net \
    --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