All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4 RFC] xorg: fix installation paths (branch yem/xorg)
Date: Mon, 2 Nov 2015 00:36:07 +0100	[thread overview]
Message-ID: <20151102003607.1fa9f695@gmx.net> (raw)
In-Reply-To: <cover.1446416019.git.yann.morin.1998@free.fr>

Hello Yann,

On Mon,  2 Nov 2015 00:00:09 +0100, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Hello All!
> 
> This series is an attempt to fix the installation paths of many
> Xorg-related packages.
> 
> *This is an RFC.*  There is an alternate proposal after the explanations
> on the series.
> 
> The new pkconf bumped in d7f6d320 introduced a change in behaviour: all
> path variables returned by pkgconf are now prefixed with the sysroot
> directory.
> 

...this commit breaks some other packages too, see [1] for libv4l example.

This commit removed a patch named '0002-fix-double-sysroot.patch', I think
this patch should somehow be forward ported to the new pkconf packet...

Regards,
Peter

[1] http://lists.busybox.net/pipermail/buildroot/2015-October/141429.html

  parent reply	other threads:[~2015-11-01 23:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01 23:00 [Buildroot] [PATCH 0/4 RFC] xorg: fix installation paths (branch yem/xorg) Yann E. MORIN
2015-11-01 23:00 ` [Buildroot] [PATCH 1/4 RFC] package/x11r7: introduce X11-global configure options Yann E. MORIN
2015-11-01 23:00 ` [Buildroot] [PATCH 2/4 RFC] package/x11r7/*: fixup all install paths Yann E. MORIN
2015-11-01 23:00 ` [Buildroot] [PATCH 3/4 RFC] core/pkg-generic: allow step hooks to fail a step Yann E. MORIN
2015-11-01 23:00 ` [Buildroot] [PATCH 4/4 RFC] core/pkg-generic: check proper package installation Yann E. MORIN
2015-11-01 23:36 ` Peter Seiderer [this message]
2015-11-02 10:38   ` [Buildroot] [PATCH 0/4 RFC] xorg: fix installation paths (branch yem/xorg) Gustavo Zacarias
2015-11-02 17:19     ` Peter Seiderer
2015-11-02 17:33       ` Yann E. MORIN
2015-11-02 18:04       ` Gustavo Zacarias

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=20151102003607.1fa9f695@gmx.net \
    --to=ps.report@gmx.net \
    --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.