From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] toolchain/helper: don't follow symlinks when copying libs to target
Date: Mon, 30 May 2016 09:03:30 +0200 [thread overview]
Message-ID: <87vb1w2fjx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LX3RRscc9VFy-5WGROHCD-qjG=hMzP2R5uXnJQX8JDwQA@mail.gmail.com> (Thomas De Schampheleire's message of "Mon, 30 May 2016 08:58:48 +0200")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
Hi,
> I'm baffled by the statement "It seems to work without just because
> STAGING_DIR happens to be defined with a trailing slash". This must
> have been derived from the observation that things worked without
> -L/-follow and making the assumption that it must have been due to a
> trailing slash without actually verifying that.
> Anyway, if it works with plain find, all the better.
> Sorry for all this confusion.
> Let's consider it a good lesson in not making assumptions :-)
Heh ;)
Ok, I'll commit a simplified version of the patch (just dropping -L)
with an updated description - Thanks all!
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-05-30 7:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 15:17 [Buildroot] [PATCH 0/2] toolchain/external: fix installing libs to target (branch yem-ext-toolchain-fixes) Yann E. MORIN
2016-05-29 15:17 ` [Buildroot] [PATCH 1/2] toolchain/external: fix arch-subdir Yann E. MORIN
2016-05-30 21:01 ` Arnout Vandecappelle
2016-05-30 21:53 ` Yann E. MORIN
2016-05-29 15:17 ` [Buildroot] [PATCH 2/2] toolchain/helper: don't follow symlinks when copying libs to target Yann E. MORIN
2016-05-29 18:54 ` Thomas De Schampheleire
2016-05-29 21:12 ` Yann E. MORIN
2016-05-29 22:33 ` Arnout Vandecappelle
2016-05-30 6:58 ` Thomas De Schampheleire
2016-05-30 7:03 ` Peter Korsgaard [this message]
2016-05-30 20:06 ` Arnout Vandecappelle
2016-05-30 20:53 ` Peter Korsgaard
2016-05-30 15:53 ` Yann E. MORIN
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=87vb1w2fjx.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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