From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4706] New: Removing .stamp_target_installed does not trigger reinstall libraries
Date: Mon, 16 Jan 2012 14:04:55 +0000 (UTC) [thread overview]
Message-ID: <bug-4706-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4706
Summary: Removing .stamp_target_installed does not trigger
reinstall libraries
Product: buildroot
Version: 2010.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: buildroot at bluespirit.la
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I've replaced content in the target_skeleton, and thus wanted to rebuild the
rootfs.tar. I did the following:
1) rm -rf target
2) rm -rf build/.root
3) rm -rf `find build -name "\.stamp_target_installed"
4) make
On the device I got a "Kernel panic - not syncing: No init found.". The problem
was that only when removing .stamp_staging_installed and
stamps/ext-toolchain-installed also the libs on the target were installed.
It would be a great help, that removing all ".stamp_target_installed" and
".root" would create a bootable target filesystem.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-01-16 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 14:04 bugzilla at busybox.net [this message]
2012-01-31 19:56 ` [Buildroot] [Bug 4706] Removing .stamp_target_installed does not trigger reinstall libraries bugzilla at busybox.net
2014-02-21 7:43 ` bugzilla at busybox.net
2014-02-21 17:40 ` bugzilla at busybox.net
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=bug-4706-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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