From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v9] toolchain: create symlink ARCH_LIB_DIR->lib in addition to lib32/lib64->lib
Date: Tue, 19 Jan 2016 21:03:47 +0100 [thread overview]
Message-ID: <20160119210347.70ddf3b5@free-electrons.com> (raw)
In-Reply-To: <20160119182947.GB3360@free.fr>
Hello,
On Tue, 19 Jan 2016 19:29:47 +0100, Yann E. MORIN wrote:
> > I was not aware that glibc already depends on skeleton. Then indeed
> > ThomasP's reasoning is correct and the patch should be simplified. I
> > will investigate that further and resubmit.
>
> Skeleton is currently not a dependency of host-gcc-initial, so you'd
> have to make it so.
Why? As explained on IRC, the only reason why Thomas DS did create the
symlinks in host-gcc-initial is to avoid duplicating this logic in all
three C library packages. But the symlinks are really only needed
before building/installing the C libraries, as far as I'm aware. So
creating them in the skeleton is OK.
Remember: in the current situation (i.e before Thomas DS patch), the
symlinks *are* created in the skeleton. And things are working fine
today, right ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-01-19 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 12:35 [Buildroot] [PATCH v9] toolchain: create symlink ARCH_LIB_DIR->lib in addition to lib32/lib64->lib Thomas De Schampheleire
2016-01-05 12:37 ` Thomas De Schampheleire
2016-01-12 23:12 ` Romain Naour
2016-01-14 19:35 ` Thomas De Schampheleire
2016-01-17 14:45 ` Thomas Petazzoni
2016-01-19 14:15 ` Thomas De Schampheleire
2016-01-19 14:17 ` Thomas De Schampheleire
2016-01-19 14:26 ` Peter Korsgaard
2016-01-19 16:01 ` Thomas De Schampheleire
2016-01-19 18:29 ` Yann E. MORIN
2016-01-19 18:35 ` Peter Korsgaard
2016-01-19 19:40 ` Thomas De Schampheleire
2016-01-19 22:57 ` Arnout Vandecappelle
2016-01-19 23:02 ` Yann E. MORIN
2016-01-19 20:03 ` Thomas Petazzoni [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=20160119210347.70ddf3b5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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