Summary: | sys-apps/systemd-196 fails to build with minimal conf | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | richardfisher |
Component: | [OLD] Core system | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
richardfisher
2012-12-04 13:35:17 UTC
> * Failed Running autoconf !
> *
> * Include in your bugreport the contents of:
> *
> * /mnt/tmp0/gentoo/pn/portage/sys-apps/systemd-196/temp/autoconf.out
Please attach that file to this bug report. /mnt/tmp0/gentoo/pn/portage/sys-apps/systemd-196/temp/autoconf.out Now I remember, I saw this ages ago. I don't think that it picks up this dependancy as it depends on ssh pulling that in. Anyway, here it is: ***** autoconf ***** ***** PWD: /mnt/tmp0/gentoo/pn/portage/sys-apps/systemd-196/work/systemd-196 ***** autoconf configure.ac:80: error: possibly undefined macro: AC_MSG_ERROR If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:415: error: possibly undefined macro: AM_PATH_LIBGCRYPT Ahh, I saw this ages ago, and I was going to file a bug: [ebuild N ] sys-apps/systemd-196 USE="-acl -audit -cryptsetup -gcrypt -http -lzma -pam -python -qrcode (-selinux) -tcpd -vanilla -xattr" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" 0 kB Basically, I cannot have any crypto stuff in this build. It seems that systemd is pulling this in either way. I think that this is a pulse problem. I think that this was around in 195 too. I think I had to change the configure script to ignore libgrcypt. Sorry if I have wasted your time. I understand what the problem is and I will fix it in the next few hours. I'm just going to check whether any more deps are enforced like that. Thanks. I remember I configured it manually about a month ago, but I forgot about it. Its not urgent, and I can just run configure without the --crypt flag from memory.
Thanks again for the speedy reply
> I understand what the problem is and I will fix it in the next few hours.
> I'm just going to check whether any more deps are enforced like that.
I have committed a cheap hack which should handle it. If it doesn't, please do not hesitate from reopening the bug. |