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!
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!
FS#14871 - Problem with autoconf / autoreconf
Attached to Project:
Arch Linux
Opened by uvok (uvok) - Friday, 29 May 2009, 09:52 GMT
Last edited by Jan de Groot (JGC) - Friday, 29 May 2009, 17:44 GMT
Opened by uvok (uvok) - Friday, 29 May 2009, 09:52 GMT
Last edited by Jan de Groot (JGC) - Friday, 29 May 2009, 17:44 GMT
|
DetailsDescription:
There is a problem in autoconf / autoreconf . When compiling the git version of bti (git://github.com/gregkh/bti.git), it says: http://dpaste.com/48935/ Additional info: autoconf and curl are installed: $ pacman -Q autoconf curl autoconf 2.63-1 curl 7.19.5-1 Steps to reproduce: 1. Download git version of bti: $ git clone git://github.com/gregkh/bti.git 2. change in bti directory 3. run ./autogen.sh Above error should display... Anyway, there is NO problem with the autogen.sh in the git-repo of bti, because it works fine on gentoo. |
This task depends upon
And why isn't the m4-file included in curl?
The m4 file isn't included by default upstream, there's an upstream bugreport about that open for 2 years without any action. Most distributions just copy the file into the right directory, but as this is the first bugreport we're getting about it, this isn't done from our package. I'll upload a fixed curl package later today.