Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 toolchain build failure
Date: Tue, 13 Aug 2013 08:15:42 +0200	[thread overview]
Message-ID: <5209CF0E.6080503@mind.be> (raw)
In-Reply-To: <20130808195932.318f5903@skate>

On 08/08/13 19:59, Thomas Petazzoni wrote:
> Dear Simon Dawson,
>
> On Thu, 8 Aug 2013 17:18:24 +0100, Simon Dawson wrote:
>
>> On 8 August 2013 11:56, Gustavo Zacarias <gustavo@zacarias.com.ar> wrote:
>>> 1) Reinstate patches in the appropiate place since uclibc was packaged.
>>> 2) Probably add various "depends on !BR2_avr32" in packages that need
>>> newer syscalls (alternatively add a ton of backports for uclibc 0.9.31
>>> from newer releases).
>>> 3) Revert startfiles cleanup to the old manual way, adding new
>>> exceptions/modes for the noMMU crowd (it wasn't handled before) - or
>>> alternatively also patch the uclibc 0.9.31 makefile to make it more
>>> 0.9.32/33-ish like.
>>
>> That doesn't sound too bad. I'm happy to do this work, if appropriate.
>> Perhaps your point #2 will not be necessary in the short term...?
>
> Ok, so let's do this maybe?
>
> I think #2 is necessary, we already have some packages that use
> syscalls that aren't provided by uClibc 0.9.31. But ok, it's just a
> matter of adding another bunch of "depends on !BR2_avr32", it's not
> fun, but it's not a big deal either.
>
> As long as someone is interested in keeping AVR32 support in place, and
> is willing to do some effort to keep this support in a reasonably good
> shape in upstream Buildroot, I'm fine with keeping it.

  What about just not including it in the autobuilders, and adding a big 
comment in the top-level menuconfig saying that AVR32 is not really 
supported and things might break?

  I think it would be good if Simon, Alexander and Thiago can use 
upstream buildroot without custom forks, but if these are the only users 
then it's not really needed to include it in the autobuilders IMHO.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-08-13  6:15 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05 12:01 [Buildroot] AVR32 toolchain build failure Thomas De Schampheleire
2013-08-05 12:29 ` Thomas De Schampheleire
2013-08-06  9:27   ` Alexander Lukichev
2013-08-06  9:39     ` Alexander Lukichev
2013-08-06 14:40     ` Thomas De Schampheleire
2013-08-06 15:03       ` Thomas De Schampheleire
2013-08-08 15:35   ` Alexander Lukichev
2013-08-06 17:54 ` Thomas Petazzoni
2013-08-06 19:33   ` Thomas De Schampheleire
2013-08-07  7:05     ` Thomas De Schampheleire
2013-08-07 15:20       ` Thomas Petazzoni
2013-08-07 16:01         ` Thomas De Schampheleire
2013-08-07 18:20           ` Thomas De Schampheleire
2013-08-07 22:07             ` Thomas Petazzoni
2013-08-08  5:55               ` Thomas De Schampheleire
2013-08-08  7:21                 ` Simon Dawson
2013-08-08  8:03                   ` Thomas Petazzoni
2013-08-08 10:56                     ` Gustavo Zacarias
2013-08-08 16:18                       ` Simon Dawson
2013-08-08 17:57                         ` Gustavo Zacarias
2013-08-08 17:59                         ` Thomas Petazzoni
2013-08-13  6:15                           ` Arnout Vandecappelle [this message]
2013-08-08  8:12                   ` Thomas De Schampheleire
2013-08-08 16:09                     ` Simon Dawson
2013-08-08 17:34                       ` Thomas De Schampheleire
2013-08-08 17:57                         ` Thomas Petazzoni
2013-08-08 18:05                           ` Thomas De Schampheleire
2013-08-08 19:42                         ` Simon Dawson
2013-08-08 20:09                           ` Thomas De Schampheleire
2013-08-08 20:24                             ` Thomas De Schampheleire
2013-08-08 22:22                               ` Thiago A. Corrêa
2013-08-09  4:51                               ` Alexander Lukichev
2013-08-09  7:16                             ` Simon Dawson
2013-08-09 11:12                               ` Thomas De Schampheleire
2013-08-09 20:29                                 ` Thomas Petazzoni
2013-08-09 22:34                                   ` Gustavo Zacarias
2013-08-08  7:29                 ` Alexander Lukichev
2013-08-08  8:13                   ` Thomas De Schampheleire
  -- strict thread matches above, loose matches on Subject: below --
2013-11-13 21:36 Thomas Petazzoni
2013-11-14  8:53 ` Simon Dawson
2013-11-14  9:10   ` Thomas Petazzoni
2013-11-15  8:58     ` Simon Dawson

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=5209CF0E.6080503@mind.be \
    --to=arnout@mind.be \
    --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