From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] make clean (did not really clean)
Date: Fri, 10 Jan 2014 07:26:26 +0800 [thread overview]
Message-ID: <20140110072626.0532ebf2@skate> (raw)
In-Reply-To: <CAPFcPT+R7f7+iJokS2cm-bFqtcsETy03FTKvSaSuft9HuZC57w@mail.gmail.com>
Dear Mau Z,
On Thu, 9 Jan 2014 14:40:20 +0200, Mau Z wrote:
> I just want to share some information (maybe known to all):
>
> I did several experiments in order to build a Linux image (with build-root
> 13.05).
> In one of them I have added udev to the image. later on I have removed udev
> from the image.
> But, actually I was not removed whatever I did, it was still there on the
> next boot (I could see it in dmesg).
>
> make clean
> delete every thing from the target
No, "make clean" does not only removes the target stuff. It removes
*everything* that was built, i.e everything that was in output/.
> The only thing that helped was "make distclean"
> Warning about "make distclean" : it deletes ALL files which where not part
> of the build-root distribution (This is it's design). So, one should copy
> text files and config files to a temporary location before issuing "make
> distclean".
This is not expected. "make clean" should clearly be sufficient.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-01-09 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 12:40 [Buildroot] make clean (did not really clean) Mau Z
2014-01-09 23:26 ` Thomas Petazzoni [this message]
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=20140110072626.0532ebf2@skate \
--to=thomas.petazzoni@free-electrons.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