From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/xorgproto: enable legacy
Date: Sun, 23 Jun 2019 12:46:42 +0200 [thread overview]
Message-ID: <20190623124642.2186a8b6@windsurf> (raw)
In-Reply-To: <20190623081342.6098-1-fontaine.fabrice@gmail.com>
Fabrice, Bernd,
On Sun, 23 Jun 2019 10:13:42 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> xproxymngproto is needed by xfindproxy but it is now disabled by default
> Enable it thanks to --enable-legacy
>
> Fixes:
> - http://autobuild.buildroot.org/results/4b21400c36e8ba7a8222f9da962f79e42c6146d3
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/x11r7/xorgproto/xorgproto.mk | 2 ++
> 1 file changed, 2 insertions(+)
I've applied to master, as your patch is the most direct solution for
the build issue. However, if this protocol is now considered legacy,
perhaps we should simply drop the xfindproxy package ? I doubt it is
used at all...
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-06-23 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 8:13 [Buildroot] [PATCH 1/1] package/xorgproto: enable legacy Fabrice Fontaine
2019-06-23 10:46 ` Thomas Petazzoni [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=20190623124642.2186a8b6@windsurf \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox