Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48766 - add make-dependency qrencode

Attached to Project: Arch Linux
Opened by Janis König (LeonardK) - Thursday, 31 March 2016, 09:23 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 03 April 2016, 15:33 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
It seems that systemd depends on qrencode by default when building target journalctl.

Additional info:
* package version(s): 194+
* build-log:

src/journal/journal-qrcode.c:92: error: undefined reference to 'QRcode_encodeString'
src/journal/journal-qrcode.c:133: error: undefined reference to 'QRcode_free'
collect2: error: ld returned 1 exit status
Makefile:10914: recipe for target 'journalctl' failed
make[2]: *** [journalctl] Error 1
Makefile:18496: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
Makefile:9207: recipe for target 'all' failed
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...

* also see here:
https://lists.fedoraproject.org/pipermail/devel/2012-October/172163.html


Steps to reproduce:
I actually tried this with lib32-systemd but it I assume this is also the case for the non-multilib package. If not, it should be fixed there.

If that's the case we actually seem to need a lib32-qrencode package if we want to build lib32-qrencode (I did one for me here: https://github.com/LeonardKoenig/PKGBUILD_lib32-qrencode)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 03 April 2016, 15:33 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Thursday, 31 March 2016, 15:57 GMT
Build in a clean chroot. Does it still happen?
Comment by Janis König (LeonardK) - Sunday, 03 April 2016, 14:03 GMT
My bad. It seems that it looks for qrencode in the configure-script and possibly finds the 64-bit qrencode libs but obviously fails to link to them because of the wrong architecture.

Is it considered good style to still add "--disable-qrencode" to the PKGBUILD even if it's unnecessary under a clean chroot?
Comment by Doug Newgard (Scimmia) - Sunday, 03 April 2016, 15:33 GMT
Packages in the official repos are written to be built in a chroot.

Loading...