From: Matthew Palmer <mpalmer@hezmatt.org>
To: openembedded-devel@lists.openembedded.org
Subject: What's with the symlinks?
Date: Fri, 29 Dec 2006 11:11:29 +1100 [thread overview]
Message-ID: <20061229001129.GA5501@hezmatt.org> (raw)
Everywhere I go while assembling my OE build tree, I see admonishments not
to use a path that has symlinks in it. For such a major problem, the only
real information on the actual problem is a fairly cryptic entry in the FAQ,
about a failure to build libtool-native.
Being an intensely curious kind of person, and not enjoying arbitrary
limits, I'm very interested to know what the *real* reason behind being so
strongly against the much-maligned symlink. Can anyone enlighten me?
- Matt
--
English is about as pure as a cribhouse whore. We don't just borrow
words; on occasion, English has pursued other languages down alleyways
to beat them unconscious and rifle their pockets for new vocabulary."
-- James D. Nicoll, resident of rec.arts.sf.written
next reply other threads:[~2006-12-29 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 0:11 Matthew Palmer [this message]
2006-12-29 0:20 ` What's with the symlinks? Robert Wörle
2006-12-29 5:51 ` jack-oe
2006-12-29 6:15 ` Matthew Palmer
2006-12-29 8:16 ` Koen Kooi
2006-12-29 12:12 ` Richard Purdie
2007-01-06 3:07 ` Jamie Lenehan
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=20061229001129.GA5501@hezmatt.org \
--to=mpalmer@hezmatt.org \
--cc=openembedded-devel@lists.openembedded.org \
/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