Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] arch support
Date: Mon, 12 Jan 2009 10:22:57 +0100	[thread overview]
Message-ID: <878wpgj2tq.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090112090745.GB25148@mx.loc> (Bernhard Reutner-Fischer's message of "Mon\, 12 Jan 2009 10\:07\:45 +0100")

>>>>> "Bernhard" == Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> writes:

Hi,

 >> Status:
 >> 
 >> alpha: broken in libpthread

 Bernhard> alpha currently only supports static builds and no threads, IIRC.

Ok, I'll fixup Kconfig deps then.

 >> arm: ok
 >> armeb: ok
 >> avr32: ok (uclibc-0.9.29-avr32, binutils-2.17-avr32, gcc-4.2.2-avr32)
 >> cris: broken in kernel headers

 Bernhard> This was already fixed, build tested fine for me some time ago.

I'll try your tree and port over fixes if needed.

 >> m68k: gcc ICE

 Bernhard> This is fixed with gcc trunk (i.e. 4.4.0).

Ok, we won't get that in BR before the release, so I'll mark it as
BROKEN for now.

 >> mips: ok
 >> mipsel: ok
 >> nios2: broken in kernel headers

 Bernhard> Would need love as it's a bit outdated.

Exactly, and apparently no one cares, so I'll mark it as BROKEN for
now. Is nios2 support evan available in upstream gcc?

 >> powerpc: ok
 >> s390: broken in uclibc

 Bernhard> s/broken/not yet supported/

True, but the outcome is the same ;)

 >> sh4: ok
 >> sh64: broken in kernel headers (merged with sh?)

 Bernhard> both sh64 and sh* build fine for me.

Ok, will check.

 >> x86_64: broken in uclibc

 Bernhard> works for me. What's failing?

uclibc build - See bottom of http://uclibc.org/~jacmet/br/x86_64.log

 >> - alpha: I'll retry with the "new" pthreads and see if that works
 >> - ia64 and sparc issue seems similar, will ask on the uclibc list
 >> - sh64: Anyone knows if that got merged with sh4 like powerpc did?

 Bernhard> there are SH and SH64. SH[234] are just SH variants -- think
 Bernhard> i?86 or mips?e{l,b}

Yes, but the kernel only has arch/sh - Should that also be used for
sh64?

 >> - s390: Shouldn't really have been added in the first place as there's
 >> no uclibc support. Will remove (Bernhard agrees)

 Bernhard> Strictly speaking this should depend on
 Bernhard> !BR2_TOOLCHAIN_BUILDROOT until it is supported in uClibc. I
 Bernhard> agree that it could just me removed from BR for now.

Ok, will do.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-01-12  9:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12  8:54 [Buildroot] arch support Peter Korsgaard
2009-01-12  9:00 ` Hans-Christian Egtvedt
2009-01-12  9:08   ` Peter Korsgaard
2009-01-12 10:33   ` Ulf Samuelsson
2009-01-12 10:35   ` Ulf Samuelsson
2009-01-12  9:07 ` Bernhard Reutner-Fischer
2009-01-12  9:22   ` Peter Korsgaard [this message]
2009-01-12 10:59 ` Hinko Kocevar
2009-01-12 11:05   ` Peter Korsgaard
2009-01-12 12:48     ` Hinko Kocevar
2009-01-12 20:17       ` Peter Korsgaard
2009-01-12 14:31 ` Hamish Guthrie
2009-01-12 14:38   ` Peter Korsgaard
2009-01-13  9:04     ` Hamish Guthrie
2009-01-13 11:40       ` Hinko Kocevar
2009-01-15 22:01     ` 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=878wpgj2tq.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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