Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Steele <jsteele@coloradocollege.edu>
To: buildroot@busybox.net
Subject: [Buildroot] make rebuilds cross tools every time ?
Date: Mon, 30 Mar 2009 19:57:32 -0600	[thread overview]
Message-ID: <1238464652.5157.44.camel@localhost.localdomain> (raw)

Hi,

I'm brand new to buildroot, and so far I'm very pleased with it.  One
problem I've been having is that it seems to rebuild uClibc and the
cross compiler/toolchain *every time* I type "make".

For example, tar-1.18 failed to compile, so I edited tar.mk to bump the
version up to 1.20.  Then I did:

# rm -rf tar-1.18
# make

Before I find out if the new version of tar compiles (it does, BTW...),
I have to wait for the whole toolchain to be rebuilt.

Am I doing something wrong ?  Shouldn't the toolchain be independent of
target apps ?


THx


BTW, I'm using buildroot-2009.02, building for armeb, host is x86.

             reply	other threads:[~2009-03-31  1:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  1:57 Jeff Steele [this message]
2009-03-31 17:16 ` [Buildroot] make rebuilds cross tools every time ? Lloyd Sargent

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=1238464652.5157.44.camel@localhost.localdomain \
    --to=jsteele@coloradocollege.edu \
    --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