From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12276] make clean/distclean does not remove BR2_DL_DIR and BR2_HOST_DIR
Date: Wed, 23 Oct 2019 20:47:24 +0000 [thread overview]
Message-ID: <bug-12276-163-poNFLM18yg@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12276-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12276
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
For BR2_DL_DIR, this is clearly an intended behavior.
However, for BR2_HOST_DIR, it does remove it properly. See:
$ grep ^BR2_HOST_DIR .config
BR2_HOST_DIR="/tmp/foobar-host"
$ ls /tmp/foobar-host/
arm-buildroot-linux-uclibcgnueabi bin etc include lib lib64 opt share
usr
$ make clean
rm -rf /home/thomas/projets/buildroot/output/target
/home/thomas/projets/buildroot/output/images /tmp/foobar-host
/home/thomas/projets/buildroot/output/host \
/home/thomas/projets/buildroot/output/build
/home/thomas/projets/buildroot/output/staging \
/home/thomas/projets/buildroot/output/legal-info
/home/thomas/projets/buildroot/output/graphs
$ ls /tmp/foobar-host/
ls: cannot access '/tmp/foobar-host/': No such file or directory
I used "make clean", but "make distclean" implies "make clean".
So I think it all works as intended.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2019-10-23 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 16:50 [Buildroot] [Bug 12276] New: make clean/distclean does not remove BR2_DL_DIR and BR2_HOST_DIR bugzilla at busybox.net
2019-10-23 20:47 ` bugzilla at busybox.net [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=bug-12276-163-poNFLM18yg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.