From: Christian Melki <christian.melki@t2data.com>
To: Michael Olbrich <m.olbrich@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] xorg-server meson build.
Date: Wed, 8 Sep 2021 19:31:10 +0200 [thread overview]
Message-ID: <7e6908a3-6049-0f1d-d9ca-99ec5c8586cc@t2data.com> (raw)
In-Reply-To: <20210908141052.GR4027748@pengutronix.de>
On 9/8/21 4:10 PM, Michael Olbrich wrote:
> On Wed, Sep 08, 2021 at 02:51:03PM +0200, Christian Melki wrote:
>> I'm having trouble building xorg-server with meson.
>>
>> Getting various non-constructive errors.
>> ../xorg-server-1.20.10/include/meson.build:175:10: ERROR: 'not-found' is not
>> a pkgconfig dependency
>>
>> ../xorg-server-1.20.10/hw/xfree86/meson.build:101:0: ERROR: '' is not a
>> static library.
>>
>> I reverted the "version bump" below and I'm not having any problems with the
>> autotools version. Upgraded to 1.2.10 with autotools.
>>
>> https://git.pengutronix.de/cgit/ptxdist/commit/rules/xorg-server.make?id=b111e5a8938b8581aecc809ec9df5b1b58e77a8f
>
> It's probably a bug in the xorg meson rules triggered by an unusual
> combination of options. Neither upstream xorg-server nor the package in
> ptxdist are well maintained.
>
Meaning? I should revert the meson variant and try to maintain the
package or "we dropped this, nobody uses xorg anymore?"
The combinations are pretty much the default ones that get selected from
dependencies.
And I like to think that xorg-server is still very much a thing. Atleast
on embedded? :)
> Michael
>
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-09-08 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 12:51 Christian Melki
2021-09-08 14:10 ` Michael Olbrich
2021-09-08 17:31 ` Christian Melki [this message]
2021-09-29 9:26 ` Michael Olbrich
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=7e6908a3-6049-0f1d-d9ca-99ec5c8586cc@t2data.com \
--to=christian.melki@t2data.com \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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