On 1/5/20 6:08 PM, n...@disroot.org wrote: >> So the question then is, what is this resolving to? >> checking for bash... >> /gnu/store/whkq7f2d702hqnrdd2cqskqxdx267283-profile/bin/bash > >> It needs to be bash >= 4.4.0, and we have a check which is supposed to >> enforce this: >> https://git.archlinux.org/pacman.git/tree/configure.ac?h=v5.2.1#n201 >> What version is your bash program, and why might it be refusing to >> recognize this bash syntax? > > The bash version is 5.0.7 > > $ /gnu/store/whkq7f2d702hqnrdd2cqskqxdx267283-profile/bin/bash --version > GNU bash, version 5.0.7(1)-release (x86_64-unknown-linux-gnu)
Then I cannot understand why it is complaining here! Do you get the same error when you manually run this: $ /gnu/store/whkq7f2d702hqnrdd2cqskqxdx267283-profile/bin/bash -O extglob -n ./scripts/libmakepkg/executable/checksum.sh >> Why is this happening so often: > >> /gnu/store/whkq7f2d702hqnrdd2cqskqxdx267283-profile/include/stdlib.h:257:4: >> warning: ISO C does not support the ‘_Float64x’ type [-Wpedantic] > > --pedantic is a GCC flag which causes every non-standard C to raise an > error, even though it may be an available extension in GCC. And, > -Wpedantic will warn about these deviations from the standard. Yeah... but the problem here is that you're generating pedantic warnings for lacking ISO C conformance in your libc headers, which is just plain useless. Might as well disable all warnings. > Despite the errors and warnings, it appears that I have a working > pacman. Thanks a lot, Eli. If you only build lib/libalpm/ and src/pacman/ then sure. Do you need a working makepkg too, though? > $ pacman --version > > .--. Pacman v5.2.1 - libalpm v12.0.1 > / _.-' .-. .-. .-. Copyright (C) 2006-2019 Pacman Development Team > \ '-. '-' '-' '-' Copyright (C) 2002-2006 Judd Vinet > '--' > This program may be freely redistributed under > the terms of the GNU General Public License. > > Thanks, > Amar > -- Eli Schwartz Bug Wrangler and Trusted User
signature.asc
Description: OpenPGP digital signature