From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11411] check-uniq-files issue
Date: Sat, 20 Oct 2018 18:46:36 +0000 [thread overview]
Message-ID: <bug-11411-163-pn3S8JkzE6@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11411-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11411
--- Comment #3 from Arnout Vandecappelle <arnout@mind.be> ---
The originally reported problem actually only occurs when you do a
package-reinstall. Not really the most important use case I'd say. If you do a
package rebuild, it works correctly.
For the *.la files, the problem indeed occurs, but it already occurs on the
first run. Indeed, after every package, we fix up the .la files, and even if
they are not really modified, their timestamp is updated. So that really has to
be fixed. However, a better fix is to not update all the .la files, but only
the .la files really touched by that package.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-10-20 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 15:37 [Buildroot] [Bug 11411] New: check-uniq-files issue bugzilla at busybox.net
2018-10-20 12:17 ` [Buildroot] [Bug 11411] " bugzilla at busybox.net
2018-10-20 16:33 ` bugzilla at busybox.net
2018-10-20 18:46 ` bugzilla at busybox.net [this message]
2018-10-20 18:59 ` bugzilla at busybox.net
2018-10-20 22:16 ` bugzilla at busybox.net
2018-10-22 7:20 ` [Buildroot] [Bug 11411] check-uniq-files target issue bugzilla at busybox.net
2018-10-22 7:37 ` bugzilla at busybox.net
2019-02-15 22:06 ` bugzilla at busybox.net
2019-10-09 15:51 ` bugzilla at busybox.net
2019-10-31 22:07 ` 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-11411-163-pn3S8JkzE6@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