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#14868 - [ratpoison] fails to build
Attached to Project:
Arch Linux
Opened by Sven Richter (sveri) - Friday, 29 May 2009, 07:04 GMT
Last edited by Ionut Biru (wonder) - Saturday, 07 November 2009, 18:01 GMT
Opened by Sven Richter (sveri) - Friday, 29 May 2009, 07:04 GMT
Last edited by Ionut Biru (wonder) - Saturday, 07 November 2009, 18:01 GMT
|
DetailsEverytime i try to build ratpoison i get the following error:
history.c:78: error: static declaration of ‘getline’ follows non-static declaration /usr/include/stdio.h:651: note: previous declaration of ‘getline’ was here make[2]: *** [history.o] Error 1 make[2]: Leaving directory `/home/sveri/abs/ratpoison/src/ratpoison-1.4.4/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/sveri/abs/ratpoison/src/ratpoison-1.4.4/src' make: *** [all-recursive] Error 1 ==> ERROR: Build Failed. Aborting... It doesnt matter if i try it by hand or the git version in aur. |
This task depends upon
Closed by Ionut Biru (wonder)
Saturday, 07 November 2009, 18:01 GMT
Reason for closing: Works for me
Saturday, 07 November 2009, 18:01 GMT
Reason for closing: Works for me
But really it doesn't affect anything, just as long as you put it before the line in history.c where it checks if HAVE_GETLINE
sorry hit enter too early
But the problem is, if i try to build the package with a package build
it always recreates the config.h. So inserting the macro there doesnt
help. Its only applicable if i compile and install by hand.
And besides that, the problem must be somewhere else, i think
in the generation of the config.h.
I already found comparable bug with the same problem and it
did not get solved. At least not really, a workaround like the
above one is a little bit dirty.
I agree that this needs a better solution though.
To get it to build you can add this patch and run autoreconf.