All of lore.kernel.org
 help / color / mirror / Atom feed
From: Microbit_P43000 <microbit@virginbroadband.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] Still can't build workingrootfswith	crosstool-NGtoolchain
Date: Thu, 22 Apr 2010 04:25:26 +1000	[thread overview]
Message-ID: <8035C465416D4C9D8992B2CB364F236E@development> (raw)
In-Reply-To: <hqn98s$5sn$1@dough.gmane.org>

Hi Grant,

> -----Original Message-----
> From: buildroot-bounces at busybox.net [mailto:buildroot-bounces at busybox.net] On Behalf Of
> Grant Edwards
> Sent: Thursday, 22 April 2010 2:31 AM
> To: buildroot at uclibc.org
> Subject: Re: [Buildroot] Still can't build workingrootfswith crosstool-NGtoolchain
> 
> On 2010-04-21, Microbit_P43000 <microbit@virginbroadband.com.au> wrote:
> 
> > That puts my soul at rest a bit... &:). Wish I posted this many
> > months ago, oh well... I have a copy of the 'dl' dir, re-extract BR,
> > re-copy the dl directory contents and re-import my configs for
> > everything and make.
> >
> > At one stage the whole cycle took ~ 1 hour 15 mins. Common sense had
> > to prevail I guess - it's just a lot faster than chasing ghosts - it
> > seems that your experience matches the observations I made.
> 
> If it's taking that long, I suspect you're also building a toolchain
> and kernel everytime.  When I realized that partial rebuilds weren't
> practical, I switched to using an external toolchain.  With an
> external toolchain and an external download directory, doing a
> from-scratch basic rootfs build takes about 6-7 minutes on a single
> CPU, 2GHz AMD Athlon64.
> 
> I also switched to building my kernel outside of buildroot.  If you're
> doing any sort of kernel development (or just want to try
> experimenting with kernel configurations), doing the kernel builds
> with buildroot is pretty clumsy.
> 
> Once you've got a kernel configuration figured out and set in stone,
> it could be useful to have the kernel built by buildroot, but it
> doesn't seem to be a paractical way to do kernel development.
> 
> --
> Grant Edwards               grant.b.edwards        Yow! PARDON me, am I
>                                   at               speaking ENGLISH?
>                               gmail.com
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

Indeed, the time I mention is a complete make from scratch. Xcompiler, utils, libc,
busybox, rootfs, etc.... It doesn't have to include the kernel, that takes all but 5 mins.
This is on a P4 dual CPU 3 GHz (albeit with only 1 GB ram).

I've tried external tools like codesourcery (which I dislike) and arm-elf-gcc and likes.
Either I ran into sysroot problems, or their were hissies being thrown about 90% through
building, that sort of stuff - yet again off a Sherlock Holmes to figure out in scripts
where these mysterious 'issues' come from.
I can't recall - surely I must have been doing something wrong, I guess. (I've come across
clear bugs on a couple of occasions, eg. I've got 32 bit EABI and some package (Lynx with
the latest SSL extensions IIRC) incorrectly gets a perceived 64 bit environment from host
instead of target settings.... More whinging yet again that uclibc is compiled for 32 bit
only - that sort of crap.
I need to revisit getting ext tool working for me again soon.  But yes, when I get back to
that, I really have to get the ext tool going.

Thanks for the insights, Grant - much appreciated, I'll post again when I get my feet back
under desk for linux cross-compile.

Maybe a note to the authors of Buildroot here that this doesn't mean I'm not appreciating
all their effort - on the contrary ! This surely must be a massive effort which I guess
could seem thankless, given all the 'problem traffic' on here.
Too much to learn anyhoo I say :-)

Best Regards,
Kris

  reply	other threads:[~2010-04-21 18:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 14:44 [Buildroot] Still can't build working rootfs with crosstool-NG toolchain Grant Edwards
2010-04-19 16:06 ` Thomas Petazzoni
2010-04-19 18:08   ` Grant Edwards
2010-04-19 17:50 ` Peter Korsgaard
2010-04-19 18:13   ` Grant Edwards
2010-04-20 18:26 ` [Buildroot] Still can't build working rootfs with crosstool-NGtoolchain Microbit_P43000
2010-04-20 23:43   ` Ben Kloosterman
2010-04-21  8:15     ` Microbit_P43000
2010-04-21 14:06       ` Grant Edwards
2010-04-21 16:07         ` [Buildroot] Still can't build working rootfswith crosstool-NGtoolchain Microbit_P43000
2010-04-21 16:31           ` Grant Edwards
2010-04-21 18:25             ` Microbit_P43000 [this message]
2010-04-21 18:33               ` [Buildroot] Still can't build workingrootfswith crosstool-NGtoolchain Grant Edwards
2010-04-21 18:46                 ` Peter Korsgaard
2010-04-21 22:06                 ` [Buildroot] Still can't buildworkingrootfswith crosstool-NGtoolchain Microbit_P43000
2010-04-21 18:43             ` [Buildroot] Still can't build working rootfswith crosstool-NGtoolchain Peter Korsgaard
2010-04-29 10:03             ` Thomas Petazzoni
2010-04-29 10:07         ` [Buildroot] Still can't build working rootfs with crosstool-NGtoolchain Thomas Petazzoni

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=8035C465416D4C9D8992B2CB364F236E@development \
    --to=microbit@virginbroadband.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.