mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] xorg-server meson build.
Date: Wed, 29 Sep 2021 11:26:43 +0200	[thread overview]
Message-ID: <20210929092642.GB2560099@pengutronix.de> (raw)
In-Reply-To: <7e6908a3-6049-0f1d-d9ca-99ec5c8586cc@t2data.com>

On Wed, Sep 08, 2021 at 07:31:10PM +0200, Christian Melki wrote:
> 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?"

Well, I don't use it any more. But I would very much appreciate patches
that keep the package maintained.
I'd start with updating to the latest version. I took a quick look at the
meson files and at least the first issue seems to be fixed with the latest
release.

> The combinations are pretty much the default ones that get selected from
> dependencies.

I assume that you mean the defaults in PTXdist. Those are pretty much
random or just disabled by default.

> And I like to think that xorg-server is still very much a thing. Atleast
> on embedded? :)

I think we're living in different filter bubbles :-). I've not used the
xorg server in embedded projects many years.

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


      reply	other threads:[~2021-09-29  9:26 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
2021-09-29  9:26     ` Michael Olbrich [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=20210929092642.GB2560099@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --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