FS#60904 - [libwmf] needs -f added to autoreconf to build

Attached to Project: Arch Linux
Opened by Kevin Mihelich (kmihelich) - Saturday, 24 November 2018, 18:29 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 24 November 2018, 20:05 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: The package does an "autoreconf -vi -Ipatches" at the end of prepare(), but it needs the -f flag as well:
autoreconf -vif -Ipatches


Additional info:
* package version: 0.2.10-1
* log:
(CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /build/libwmf/src/libwmf-0.2.10/missing autoheader)
autoheader: warning: missing template: HAVE_EXPAT
autoheader: Use AC_DEFINE([HAVE_EXPAT], [], [Description])
autoheader: warning: missing template: HAVE_GD
autoheader: warning: missing template: HAVE_LIBJPEG
autoheader: warning: missing template: HAVE_LIBPLOT
autoheader: warning: missing template: HAVE_LIBPNG
autoheader: warning: missing template: HAVE_LIBXML2
autoheader: warning: missing template: WITHOUT_LAYERS
autoheader: warning: missing template: snprintf
autoheader: warning: missing template: vsnprintf
make: *** [Makefile:468: wmfconfig.h.in] Error 1
==> ERROR: A failure occurred in build().


Steps to reproduce: Build in a clean chroot.
This task depends upon

Closed by  Antonio Rojas (arojas)
Saturday, 24 November 2018, 20:05 GMT
Reason for closing:  Fixed
Comment by loqs (loqs) - Saturday, 24 November 2018, 18:50 GMT
Works for me using `extra-x86_64-build`
Comment by Antonio Rojas (arojas) - Saturday, 24 November 2018, 19:13 GMT
WFM too
Comment by Kevin Mihelich (kmihelich) - Saturday, 24 November 2018, 19:15 GMT
I don't see why it's working for you. It fails consistently here using makechrootpkg.
Comment by loqs (loqs) - Saturday, 24 November 2018, 19:20 GMT
Does switching the shell from zsh to bash have any effect?
Comment by Kevin Mihelich (kmihelich) - Saturday, 24 November 2018, 19:23 GMT
I only use bash here.
Comment by loqs (loqs) - Saturday, 24 November 2018, 19:26 GMT
Ah I was looking at the error message containing 'ZSH_VERSION' and was wondering if it some zsh specific code had been triggered.
Comment by Kevin Mihelich (kmihelich) - Saturday, 24 November 2018, 19:35 GMT
Still reproducible after regenerating my chroot. You should be able to see the same with a local mkarchroot with only base-devel and a makechrootpkg.
Comment by Antonio Rojas (arojas) - Saturday, 24 November 2018, 19:48 GMT
OK, can reproduce with makechrootpkg, but not with extra-x86_64-build. Weird.

Loading...