From: Peter Korsgaard <peter@korsgaard.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 15:26:28 +0100 [thread overview]
Message-ID: <87lh7l3asr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LUUwQ4yt38Cy+A5QpL+kXhGmd9iiBvJLdNA8uJDv=TpMA@mail.gmail.com> (Thomas De Schampheleire's message of "Tue, 19 Jan 2016 15:17:07 +0100")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
Hi,
>> In earlier versions of the patch, I stated that the symlink creation
>> needs to happen before gcc-initial is built. This is the reason we are
>> hooking into gcc-initial. This was also effectively the case before
>> the skeleton package was introduced.
> Small correction, the statement is:
> +# The creation of lib32/lib64 symlinks into target and staging directories
> +# needs to be done before the C library is installed.
And that's already the case, right? E.G. all packages depend on
skeleton, including the glibc/uclibc/musl packages.
E.G. from a build with an external toolchain:
1453212927:start:extract : linux
1453212938:end :extract : linux
1453212938:start:patch : linux
1453212939:end :patch : linux
1453213000:start:extract : skeleton
1453213000:end :extract : skeleton
1453213000:start:patch : skeleton
1453213000:end :patch : skeleton
1453213000:start:configure : skeleton
1453213000:end :configure : skeleton
1453213000:start:build : skeleton
1453213000:end :build : skeleton
1453213000:start:install-staging : skeleton
1453213000:end :install-staging : skeleton
1453213000:start:install-target : skeleton
1453213001:end :install-target : skeleton
1453213002:start:extract : toolchain-external
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-01-19 14:26 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 [this message]
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
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=87lh7l3asr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.