All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] core: use merged /usr in staging (branch merged-usr-staging)
Date: Sat, 28 Nov 2015 23:10:57 +0100	[thread overview]
Message-ID: <87610lpyfi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <cover.1448575841.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Thu, 26 Nov 2015 23:13:38 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > Hello All!
 > As reported by Pieterjan, when doing remote debugging with gdbserver on
 > a merged /usr setup, the remote gdb would only look for libraries in
 > staging/lib and never in staging/usr/lib.

 > This series replicates in staging the same merged /usr handling as we
 > have for target/.

 > This is implemented in the skeleton package, as it is the only easy
 > place that is guaranteed to be before all other packages *and* before
 > the toolchains.

Committed series, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2015-11-28 22:10 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
2015-11-28 16:46       ` Pieterjan Camerlynck
2015-11-28 22:10 ` Peter Korsgaard [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=87610lpyfi.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.