public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Sergii Romantsov <sergii.romantsov@gmail.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v1] meson: missed dependency of liblzma
Date: Tue, 26 Feb 2019 12:20:29 +0200	[thread overview]
Message-ID: <20190226102029.GE4038@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <CALWg4ioqQqgF7i89wFkxUP+xh4mkVJiHCiE00Yc7dgTUXqngow@mail.gmail.com>

On Tue, Feb 26, 2019 at 12:03:07PM +0200, Sergii Romantsov wrote:
> Hello, Petri.
> 
> 
> > As I understood you, just installing liblzma-dev makes the build
> > successful, right?
> 
> 
> If to be more specific, installing liblzma-dev makes meson-configuration
> successful.
> 
> Making this change just lead to better error messages when it's not
> > installed?
> 
> 
> Yes, it will show which package exactly leaked instead of unclear error.
> 
> What is the distro you're using?
> 
> 
> 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019
> x86_64 x86_64 x86_64 GNU/Linux
> 
> I think it happens due to specific of meson-dependency - how it looks for a
> package.
> So command (when liblzma-dev is absent, but liblzma5 is installed)
>  'pkg-config --cflags --libs libdw'
> gives:
> "Package liblzma was not found in the pkg-config search path.
> Perhaps you should add the directory containing `liblzma.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'liblzma', required by 'libdw', not found"
> 
> So in my understanding its just because of lack of liblzma.pc


Indeed. I checked Ubuntu 16.04's libdw-dev and it:

1) Has liblzma in Requires.private in libdw.pc
2) Does not depend on liblzma-dev

I don't see the bug reported, and I suspect it won't be fixed, with
16.04's support ending this year for the desktop version...


However, on the patch, I'll have to nak the meson.build change. Having
better error messages is not a good reason for useless dependency
declarations. I'll welcome a patch that makes dependency failures
point to the Dockerfiles, though.


-- 
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-02-26 10:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-25 13:23 [igt-dev] [PATCH i-g-t v1] meson: missed dependency of liblzma Sergii Romantsov
2019-02-25 14:31 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-02-25 18:12 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-26  9:46 ` [igt-dev] [PATCH i-g-t v1] " Petri Latvala
2019-02-26 10:03   ` Sergii Romantsov
2019-02-26 10:20     ` Petri Latvala [this message]
2019-04-12 13:36       ` [igt-dev] [PATCH i-g-t v2] " Sergii Romantsov
2019-04-15  8:23         ` Petri Latvala
2019-04-15  8:25           ` Petri Latvala
2019-04-12 13:41       ` [igt-dev] [PATCH i-g-t v1] " Sergii Romantsov
2019-04-12 16:11 ` [igt-dev] ✓ Fi.CI.BAT: success for meson: missed dependency of liblzma (rev2) Patchwork
2019-04-12 18:18 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

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=20190226102029.GE4038@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=sergii.romantsov@gmail.com \
    /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