Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkgconf: bump to 1.5.3, change upstream
Date: Sun, 9 Dec 2018 21:03:37 +0100	[thread overview]
Message-ID: <20181209200337.GF3383@scaer> (raw)
In-Reply-To: <20181209195931.GE3383@scaer>

Bernd, All,

(Damn, I was not finished typing my mail, I was to quick at sending
it... Sorry for the noise...)

On 2018-12-09 20:59 +0100, Yann E. MORIN spake thusly:
> On 2018-12-09 19:31 +0100, Bernd Kuhls spake thusly:
> > Am Sat, 08 Sep 2018 22:05:07 +0200 schrieb Thomas Petazzoni:
> > > Of course, updating pkgconf has the potential of breaking lots of
> > > things, that's why I would suggest to update early in the development
> > > cycle, to leave us enough time to resolve issues.
> > libxcb got broken due to this bump:
> > http://autobuild.buildroot.net/?reason=libxcb-1.13
> > 
> > Libxcb configure checks for the variable xcbincludedir of the xcb-proto 
> > package during configure:
> > https://cgit.freedesktop.org/xcb/libxcb/tree/configure.ac#n75
> > 
> > This results in
> > 
> > $ /home/bernd/buildroot/br8_ffmpeg3_kodi17_github/output/host/bin/pkg-
> > config --variable=xcbincludedir xcb-proto
> > 
> > /home/bernd/buildroot/br8_ffmpeg3_kodi17_github/output/host/x86_64-
> > buildroot-linux-uclibc/sysroot/home/bernd/buildroot/
> > br8_ffmpeg3_kodi17_github/output/host/bin/../x86_64-buildroot-linux-
> > uclibc/sysroot/usr/share/xcb
> > 
> > Please note that "/home/bernd/buildroot/..." is present twice in the 
> > pkgconfig result.
> 
> Have you noticed that it is us that are adding the sysroot to the
> xcb-proto.pc file:
> 
>     https://git.buildroot.org/buildroot/tree/package/x11r7/xcb-proto/xcb-proto.mk#n18
> 
> and thus maybe we need to dfrop this tweak now that pkgconf does it for

s/dfrop/drop/

> us?

BTW, that tweak was done by someone called Bernd Kuhls, in commit
862e1221d1c (xorg: Bump xcb-proto & libxcb version to 1.10). Granted,
that was back then in January 2014, now almost 5 years ago, so you're
forgiven for forgiving that! ;-)

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-12-09 20:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-08 20:05 [Buildroot] [PATCH] pkgconf: bump to 1.5.3, change upstream Thomas Petazzoni
2018-12-03 10:17 ` Yann E. MORIN
2018-12-09 15:57 ` Thomas Petazzoni
2018-12-09 18:31 ` Bernd Kuhls
2018-12-09 19:59   ` Yann E. MORIN
2018-12-09 20:03     ` Yann E. MORIN [this message]
2018-12-09 20:42       ` Bernd Kuhls

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=20181209200337.GF3383@scaer \
    --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