Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] ARCH=ppc vs powerpc
Date: Fri, 04 Apr 2008 20:02:26 +0200	[thread overview]
Message-ID: <87y77tlcr1.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <0f8401c8966c$f30cb5f0$f52f9e86@LPSC0173W> (Guillaume Dargaud's message of "Fri\, 4 Apr 2008 18\:00\:00 +0200")

>>>>> "Guillaume" == Guillaume Dargaud <dargaud@lpsc.in2p3.fr> writes:

 >>>> Ok. I don't have such an old GCC on my system so I cannot test. Maybe
 >>>> you will have more luck if you select GCC 3.4.6 in buildroot instead?

 Guillaume> OK, big system upgrade, I'm now at gcc 4.1.2 and I seem to
 Guillaume> be able to compile so far (haven't tried the kernel yet).

Great.

 Guillaume> One thing to note: changing options in menuconfig is often
 Guillaume> poorly reflected in the 'makes' underneath and no amount
 Guillaume> of 'make clean' or 'make distclean' can make it
 Guillaume> right. Restarting from a clean svn and copying the .config
 Guillaume> file works though, but that's rather a big waste of time
 Guillaume> like in the case of strip/sstrip/none for instance.

True. I most of the time just do a rm -rf *build* after changing stuff.

 Guillaume> Side question: where to best learn how to make a bootable
 Guillaume> ACE file for the Xilinx architecture from a kernel and, I
 Guillaume> assume, a bootloader ? Or in other words, how do I use the
 Guillaume> U-Boot option of buildroot ?

Hmm, I have never used the systemace stuff, have you checked Grant
Likely's wiki? (http://wiki.secretlab.ca).

For the U-boot stuff, it's probably easier to build it by hand instead
of using buildroot while you are porting it to your board / tweaking
stuff.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2008-04-04 18:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 14:16 [Buildroot] ARCH=ppc vs powerpc Guillaume Dargaud
2008-04-02 14:45 ` Peter Korsgaard
2008-04-02 16:23   ` Guillaume Dargaud
2008-04-02 16:41   ` Bernhard Fischer
2008-04-03 12:09     ` Guillaume Dargaud
2008-04-03 12:24       ` Peter Korsgaard
2008-04-03 14:20         ` Guillaume Dargaud
2008-04-03 15:09           ` Peter Korsgaard
2008-04-03 15:34             ` Guillaume Dargaud
2008-04-04  8:03               ` Peter Korsgaard
2008-04-04  9:02                 ` Guillaume Dargaud
2008-04-04  9:37                   ` Peter Korsgaard
2008-04-04 10:28                     ` Guillaume Dargaud
2008-04-04 11:07                       ` Peter Korsgaard
2008-04-04 12:30                         ` Guillaume Dargaud
2008-04-04 13:37                           ` Peter Korsgaard
2008-04-04 14:10                           ` Bernhard Fischer
2008-04-04 14:18                             ` Peter Korsgaard
2008-04-04 16:00                             ` Guillaume Dargaud
2008-04-04 18:02                               ` Peter Korsgaard [this message]

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=87y77tlcr1.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