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#16686 - [9base] troff segfaults.
Attached to Project:
Community Packages
Opened by Ramil (gravicappa) - Friday, 16 October 2009, 09:27 GMT
Last edited by Chris Brannon (cmb) - Friday, 16 October 2009, 18:46 GMT
Opened by Ramil (gravicappa) - Friday, 16 October 2009, 09:27 GMT
Last edited by Chris Brannon (cmb) - Friday, 16 October 2009, 18:46 GMT
|
DetailsDescription:
In 9base-4-1 troff segfaults even when invoked with no arguments. It seems that wrong CFLAGS are provided during compilation of the package. Additional info: * package version(s) 9base-4-1-i686 Steps to reproduce: sudo pacman -S 9base /opt/plan9/bin/troff New PKGBUILD is attached that fixes the issue. 
PKGBUILD
(1.2 KiB)
|
This task depends upon
I'd like to know why CFLAGS are causing problems, though. Mine are just
the defaults from makepkg.conf: -march=i686 -mtune=generic -O2 -pipe.
Anyway, I'll run some more tests, upload a fix, and hopefully close this
bug in the next day or so.
CFLAGS += <values>
Then <values> are appended to makepkg.conf defaults, no need to fix makepkg.conf there.
I've made no research in CFLAGS effect, I've just used hint from post on suckless.org mailing list.