From: Yann E. MORIN <yann.morin.1998@free.fr>
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 19:29:47 +0100 [thread overview]
Message-ID: <20160119182947.GB3360@free.fr> (raw)
In-Reply-To: <CAAXf6LUqCv04ZkCH5fKwq2_0w9hBYFYXM_Bf5t1yawG1D8yeTQ@mail.gmail.com>
Thomas?, Peter, All,
On 2016-01-19 17:01 +0100, Thomas De Schampheleire spake thusly:
> On Tue, Jan 19, 2016 at 3:26 PM, Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>>> "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.
>
> Ok, so that is the missing part of the puzzle.
>
> On 2015.05, where skeleton was not yet a package, and so the situation
> upon which the original patch was based, the symlinks were made in the
> .root target. To allow for this new symlink behavior, it had to be
> moved, but it had to be before the C library. The toolchain target was
> too late, gcc-initial was voted the 'best' place at the time.
>
> 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.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-01-19 18:29 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 [this message]
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=20160119182947.GB3360@free.fr \
--to=yann.morin.1998@free.fr \
--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.