From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11701] recuuring of usr and in bin shortcuts are created
Date: Wed, 27 Feb 2019 22:44:02 +0000 [thread overview]
Message-ID: <bug-11701-163-rTh7ZjA1hT@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11701-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11701
--- Comment #1 from Peter Seiderer <ps.report@gmx.net> ---
Not much/enough information to reproduce your problem, see e.g. [1] what maybe
needed.
Please provide your .config (or defconfig) file of your build.
Try to make a clean re-build (see [2]): make clean; make
Try to show an example of what you see in the host directory, e.g.
the output of ls or find commands...
[1] http://nightly.buildroot.org/manual.html#reporting-bugs
[2] http://nightly.buildroot.org/manual.html#full-rebuild
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-02-27 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 10:45 [Buildroot] [Bug 11701] New: recuuring of usr and in bin shortcuts are created bugzilla at busybox.net
2019-02-27 22:44 ` bugzilla at busybox.net [this message]
2019-08-13 1:12 ` [Buildroot] [Bug 11701] " 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-11701-163-rTh7ZjA1hT@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