Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Gaisler sparc-leon
Date: Fri, 03 Sep 2010 16:50:06 +0200	[thread overview]
Message-ID: <878w3ivq3l.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20100903091327.v01tegjghcqso4oo@webmail.bluegenesis.com> (konrad@gaisler.com's message of "Fri, 03 Sep 2010 09:13:27 -0400")

>>>>> "konrad" == konrad  <konrad@gaisler.com> writes:

Hi,

 konrad> My shortterm goal is to get buildroot to build a linux image
 konrad> with romfs that includes libc shared and some more advanced app
 konrad> like a ssh. That should cover/test already a lot
 konrad> functionality. So far in snapgear 2.0 we only used uClibc
 konrad> static, we had made quite a few patches to uclibc, didnt submit
 konrad> them to the uclibc though. It was also a fairly old uclibc that
 konrad> we used, it seems that uclibc has gotten better in the meantime
 konrad> (while we sticked still to the old version...). I think that if
 konrad> Gaisler would switch to buildroot and Leon users would start
 konrad> using it the sparc the sparc part would be maintained and
 konrad> running.I'll press this now and will post my results

Ok, good - Shared linking on sparc indeed used to be broken as far as I
remember.

 konrad> Ps: Note at the side: If no hardware is available the
 konrad> evaluation version of the sparcleon simulator called TSIM can
 konrad> be used, so that non sparc users can run/test/verify too. ?

What about something a bit more standard like qemu-system-sparc? We're
already using qemu to test E.G. arm.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-09-03 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 13:13 [Buildroot] Gaisler sparc-leon konrad at gaisler.com
2010-09-03 14:50 ` Peter Korsgaard [this message]
2010-09-03 15:44   ` Michael S. Zick
  -- strict thread matches above, loose matches on Subject: below --
2010-09-03 15:30 konrad at gaisler.com
2010-09-02 18:44 konrad at gaisler.com
2010-09-02 21:50 ` Peter Korsgaard

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=878w3ivq3l.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