From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] rebuilding a project on older commits
Date: Sat, 26 Jan 2013 18:57:28 +0100 [thread overview]
Message-ID: <51041908.1030803@googlemail.com> (raw)
Hello,
is there a simple way to rebuild a project without the whole
crosscompiler part?
I have to search in my project why now the current output of Buildroot
isn't startable via nfs. So I want to go back and try out which commit
breaks the build, like I can do similar with git bisect in other Git
repos. Probably the busybox here is miss configured in the between time
because the current kernel config, which has also some little changes
works with an older rootfs.tar.
The current kernel with an actual rootfs ended up with
> [ 10.890000] Looking up port of RPC 100003/3 on 192.168.136.4
> [ 10.910000] Looking up port of RPC 100005/3 on 192.168.136.4
> [ 10.920000] VFS: Mounted root (nfs filesystem) on device 0:12.
> [ 10.930000] Freeing init memory: 104K
> [ 10.940000] Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
But after make <myproject>defconfig the complete crosscompiler is
rebuilded which I don't want to do because I don't have change something
on it. How to handle that?
Thanks and regards
Carsten
next reply other threads:[~2013-01-26 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 17:57 Carsten Schoenert [this message]
2013-01-27 8:30 ` [Buildroot] rebuilding a project on older commits Thomas Petazzoni
2013-01-27 9:11 ` Carsten Schoenert
2013-01-27 10:33 ` Thomas Petazzoni
2013-01-27 11:24 ` Stephan Hoffmann
2013-01-27 11:36 ` 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=51041908.1030803@googlemail.com \
--to=c.schoenert@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