From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/skeleton: also handle merged /usr in the staging
Date: Fri, 27 Nov 2015 23:48:00 +0100 [thread overview]
Message-ID: <20151127224800.GB4144@free.fr> (raw)
In-Reply-To: <5658DA6B.8040305@mind.be>
Arnout, All,
On 2015-11-27 23:34 +0100, Arnout Vandecappelle spake thusly:
> On 26-11-15 23:13, Yann E. MORIN wrote:
> > When the target uses a merged /usr setup, gdbserver will only report
> > paths in /lib to the remote gdb, which in turn will only look libraries
> > in staging/lib and never in staging/usr/lib.
> >
> > So. the mreged (or non-merged) /usr setup must be replicated in the
> > staging.
> >
> > The best solution where to do so is in the skeleton package, since it
> > is guaranteed to come before any package that installs things in the
> > staging, and even before the (internal or external) toolchain as well.
> >
> > Reported-by: Pieterjan Camerlynck <pieterjan.camerlynck@gmail.com>
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Pieterjan Camerlynck <pieterjan.camerlynck@gmail.com>
> > Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> > Cc: Peter Korsgaard <jacmet@uclibc.org>
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
>
> However, this only applies to next - shouldn't we do this on master as well?
> This will be the first time we release the merged /usr, so we should probably
> get it right...
Hmmm... Surely this patch was done against master, not next. Or did I
foobared my tree?... ;-)
Yes, I'd like we get that in master, but I'd like some testing first (of
course, I did my homework, but a note from the reporter would have been
great, too).
> Perhaps this would be a good time to move this to the
> SKELETON_USR_SYMLINKS_OR_DIRS macro and remove these directories from the skeleton.
*That* would be for next. Or after the release, since it's so close...
Thanks! :-)
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:[~2015-11-27 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 22:13 [Buildroot] [PATCH 0/2] core: use merged /usr in staging (branch merged-usr-staging) Yann E. MORIN
2015-11-26 22:13 ` [Buildroot] [PATCH 1/2] package/skeleton: parametrise the symlinks-or-mkdir macro Yann E. MORIN
2015-11-27 21:58 ` Arnout Vandecappelle
2015-11-27 22:50 ` Yann E. MORIN
2015-11-26 22:13 ` [Buildroot] [PATCH 2/2] package/skeleton: also handle merged /usr in the staging Yann E. MORIN
2015-11-27 22:34 ` Arnout Vandecappelle
2015-11-27 22:48 ` Yann E. MORIN [this message]
2015-11-28 16:46 ` Pieterjan Camerlynck
2015-11-28 22:10 ` [Buildroot] [PATCH 0/2] core: use merged /usr in staging (branch merged-usr-staging) Peter Korsgaard
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=20151127224800.GB4144@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox