mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2018.09.0 released
Date: Wed, 19 Sep 2018 18:51:23 +0200	[thread overview]
Message-ID: <20180919165122.GA11832@archibald.tuxnet> (raw)
In-Reply-To: <20180918141355.xi47kknjwoi3iukf@pengutronix.de>

Hi,

On Tue, Sep 18, 2018 at 04:13:55PM +0200, Michael Olbrich wrote:
> Hi,
> 
> I'm happy to announce that I've just released ptxdist-2018.09.0.
> 
> The are no big changes in this release. The pkg-config wrapper script is
> now used for host and target packages and handles all the path magic. This
> makes it possible to use sysroot-host/bin/pkg-config for host-tools in
> target packages.
> The rest is the usual mix of new packages, bugfixes and version bumps.
> 
> Thanks to all contributors and - as always - the shortlog below.
> 
> Enjoy,
> Michael Olbrich

The systemd build breaks for me with PTXdist 2018.09.0:

...
Message: Using /usr/bin/mount for mount
Message: Using /usr/bin/umount for umount
Message: Using /usr/bin/loadkeys for loadkeys
Message: Using /usr/bin/setfont for setfont
Program gperf found: YES (/home/clemens/foo/platform-bar/sysroot-host/bin/gperf)
Message: gperf len type is size_t
Has header "sys/capability.h": YES
Has header "crypt.h": YES
Has header "linux/btrfs.h": YES
Has header "linux/memfd.h": YES
Has header "linux/vm_sockets.h": YES
Has header "sys/auxv.h": YES
Has header "valgrind/memcheck.h": NO
Has header "valgrind/valgrind.h": NO
Message: maximum system UID is 999
Message: maximum system GID is 999
Dependency threads found: YES
Library rt found: YES
Library m found: YES
Library dl found: YES
Library crypt found: YES
Dependency libcap found: NO
Library cap found: YES

meson.build:808:0: ERROR:  Cross dependency 'mount' not found


The last part in meson-log.txt is:

...

Code:
 int main(int argc, char **argv) { return 0; }
Compiler stdout:

Compiler stderr:

Library cap found: YES
Determining dependency 'mount' with pkg-config executable '/home/clemens/foo/
platform-bar/sysroot-cross/bin/arm-v7a-linux-gnueabihf-pkg-config'
Called `/home/clemens/foo/platform-bar/sysroot-cross/bin/arm-v7a-li
nux-gnueabihf-pkg-config --modversion mount` -> 1

meson.build:808:0: ERROR:  Cross dependency 'mount' not found

--

This could be connected to the pkg-config changes between 2018.08.0
and 2018.09.0 (?), but I did not yet have time to bisect it.

Can you reproduce this and do you have an idea what's causing it?

About my setup:
I am using a customized OSELAS toolchain with glibc 2.28 and had to
backport one systemd upstream patch before:
https://github.com/systemd/systemd/commit/75720bff62a84896e9a0654afc7cf9408cf89a38
(But all of this works fine with PTXdist 2018.08.0)

Thanks,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2018-09-19 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18 14:13 Michael Olbrich
2018-09-19  6:38 ` Alexander Dahl
2018-09-19 13:42   ` Michael Olbrich
2018-09-19 16:51 ` Clemens Gruber [this message]
2018-09-20  8:00   ` Michael Olbrich
2018-09-20 13:07     ` Clemens Gruber
2018-09-21  8:17       ` Michael Olbrich
2018-09-21 13:43         ` Clemens Gruber

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=20180919165122.GA11832@archibald.tuxnet \
    --to=clemens.gruber@pqgruber.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