From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] spurious rebuilds? Re: svn commit: trunk/buildroot: target/linux toolchain/uClibc
Date: Fri, 28 Sep 2007 22:27:09 +0200 [thread overview]
Message-ID: <20070928202708.GV20951@aon.at> (raw)
In-Reply-To: <20070928194327.E4F34A69E5@busybox.net>
On Fri, Sep 28, 2007 at 12:43:27PM -0700, ulf at uclibc.org wrote:
>Author: ulf
>Date: 2007-09-28 12:43:26 -0700 (Fri, 28 Sep 2007)
>New Revision: 20088
>
>Log:
>Cleanup cross toolchain admin, split uclibc-menuconfig into same + uclibc-update to avoid overwriting board support file
Ulf,
With these two changes (this one and the previous that touched these),
can you please build an image (with tarroot off), and then turn tarroot
on and make again.
I'm pretty sure that this used to just regenerate the target
"filesystems" and didn't lead to a complete rebuild (that i'm currently
enjoying)..
Please confirm.
next prev parent reply other threads:[~2007-09-28 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 19:43 [Buildroot] svn commit: trunk/buildroot: target/linux toolchain/uClibc ulf at uclibc.org
2007-09-28 20:27 ` Bernhard Fischer [this message]
2007-09-29 11:40 ` [Buildroot] spurious rebuilds? " 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=20070928202708.GV20951@aon.at \
--to=rep.dot.nop@gmail.com \
--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