Skip to contentSkip to conversation

libpam-systemd not built, but enabled in systemd PACKAGECONFIG

DISCUSSION Ferry Toth 2 participants 4 messages Jun 2, 2017 – Jun 3, 2017

lore
Share & tools
lore

Ferry Toth

author
#0 lore raw

That is when building systemd with morty.

I have DISTRO_FEATURES pam set, but I find --disable-pam in the configure log.

In fact only --enable-split-usr --enable-xz and --enable-nls are set according to the log. None of these are set through PACKAGECONFIG.

And everything that is set through PACKAGECONFIG is --disabled...

It looks inverted..

What am I doing wrong?

#1 lore raw
Quoted 5 lines · Ferry Toth

That is when building systemd with morty.

I have DISTRO_FEATURES pam set, but I find --disable-pam in the configure log.

Quoted 8 lines

In fact only --enable-split-usr --enable-xz and --enable-nls are set according to the log. None of these are set through PACKAGECONFIG.

And everything that is set through PACKAGECONFIG is --disabled...

It looks inverted..

What am I doing wrong?

Can you show output of

bitbake -e systemd | grep -e "^DISTRO_FEATURES="

Quoted 6 lines

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

author
#2 lore raw
Quoted 12 lines · Khem Raj
Quoted 10 lines · Ferry Toth

That is when building systemd with morty.

I have DISTRO_FEATURES pam set, but I find --disable-pam in the configure log.

In fact only --enable-split-usr --enable-xz and --enable-nls are set according to the log. None of these are set through PACKAGECONFIG.

And everything that is set through PACKAGECONFIG is --disabled...

Quoted 7 lines
Quoted 3 lines

It looks inverted..

What am I doing wrong?

Can you show output of

bitbake -e systemd | grep -e "^DISTRO_FEATURES="

DISTRO_FEATURES="systemd alsa argp bluetooth ext2 largefile usbgadget usbhost wifi xattr zeroconf pci pam ipv4 ipv6 libc-backtrace libc-big-macros libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt
libc-crypt-ufc libc-db-aliases libc-envz
libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse
libc-getlogin libc-idn libc-inet-anl libc-libm libc-
locales libc-locale-code
libc-memusage libc-nis libc-nsswitch libc-rcmd libc-rtld-debug libc-spawn libc-streams libc-sunrpc
libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc
libc-posix-wchar-io pulseaudio bluez5 gobject-introspection-data"

But thanks for pointing this out, I had looked here before, but I had missed the following line (bitbake -e systemd | grep -e "PACKAGECONFIG="):

# $PACKAGECONFIG_pn-systemd
# set /home/ferry/tmp/edison-intel/my/edison-morty/meta-intel-edison/meta-
intel-edison-distro/conf/distro/poky-edison.conf:21
# "xz"
PACKAGECONFIG_pn-systemd="xz"

I appears I also had a line in my conf:
PACKAGECONFIG_pn-systemd = "xz"

This appears to overrule the distro features.

The conf file is a remnant of:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-edison/tree/meta-intel-edison-distro/conf/distro/poky-edison.conf

So it looks like meta-intel-edison-distro cn never have worked well.

Quoted 5 lines
Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--

#3 lore raw
Quoted 35 lines · Ferry Toth
Quoted 12 lines · Khem Raj
Quoted 10 lines · Ferry Toth

That is when building systemd with morty.

I have DISTRO_FEATURES pam set, but I find --disable-pam in the configure log.

In fact only --enable-split-usr --enable-xz and --enable-nls are set according to the log. None of these are set through PACKAGECONFIG.

And everything that is set through PACKAGECONFIG is --disabled...

Quoted 7 lines
Quoted 3 lines

It looks inverted..

What am I doing wrong?

Can you show output of

bitbake -e systemd | grep -e "^DISTRO_FEATURES="

DISTRO_FEATURES="systemd alsa argp bluetooth ext2 largefile usbgadget usbhost wifi xattr zeroconf pci pam ipv4 ipv6 libc-backtrace libc-big-macros libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt
libc-crypt-ufc libc-db-aliases libc-envz
libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse
libc-getlogin libc-idn libc-inet-anl libc-libm libc-
locales libc-locale-code
libc-memusage libc-nis libc-nsswitch libc-rcmd libc-rtld-debug libc-spawn libc-streams libc-sunrpc
libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc
libc-posix-wchar-io pulseaudio bluez5 gobject-introspection-data"

Quoted 8 lines

But thanks for pointing this out, I had looked here before, but I had missed the following line (bitbake -e systemd | grep -e "PACKAGECONFIG="):

# $PACKAGECONFIG_pn-systemd
# set /home/ferry/tmp/edison-intel/my/edison-morty/meta-intel-edison/meta-
intel-edison-distro/conf/distro/poky-edison.conf:21
# "xz"
PACKAGECONFIG_pn-systemd="xz"

hmm they probably meant to append and not override

Quoted 6 lines

I appears I also had a line in my conf:
PACKAGECONFIG_pn-systemd = "xz"

This appears to overrule the distro features.

yes, thats the expected behavior for this assignment.

Quoted 17 lines

The conf file is a remnant of:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-edison/tree/meta-intel-edison-distro/conf/distro/poky-edison.conf

So it looks like meta-intel-edison-distro cn never have worked well.

Quoted 5 lines
Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto