From: Arnout Vandecappelle <arnout@mind.be>
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 23:57:46 +0100 [thread overview]
Message-ID: <569EBF6A.4080208@mind.be> (raw)
In-Reply-To: <CAAXf6LVSwy5ozhJ4cYrSDF5gXBNEkjEs9ej_L2TkLa5a4avV8g@mail.gmail.com>
On 19-01-16 20:40, Thomas De Schampheleire wrote:
>
> On Jan 19, 2016 19:35, "Peter Korsgaard" <peter@korsgaard.com
> <mailto:peter@korsgaard.com>> wrote:
>>
>> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr
> <mailto:yann.morin.1998@free.fr>> writes:
>>
>> Hi,
>>
>> >> 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.
>>
>> Ahh yes, we only add it for target packages.
>
> I did 'make clean toolchain' on x86-64 qemu defconfig but with glibc, and at the
> end I noticed that skeleton was built and the symlinks were correctly created.
> So which package had the skeleton dependency? (Don't have a buildroot near me ATM)
glibc is a target package so depends on skeleton (see pkg-generic.mk, search
for skeleton).
Regards,
Arnout
>
> /Thomas
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-01-19 22:57 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 [this message]
2016-01-19 23:02 ` Yann E. MORIN
2016-01-19 20:03 ` Thomas Petazzoni
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=569EBF6A.4080208@mind.be \
--to=arnout@mind.be \
--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