Arch Linux

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!
Tasklist

FS#3521 - flex/bison and glibc inconsistent

Attached to Project: Arch Linux
Opened by Florian Merz (florian) - Thursday, 24 November 2005, 12:15 GMT
Last edited by arjan timmerman (blaasvis) - Saturday, 25 March 2006, 22:56 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The current versions of flex/bison in Arch (bison-2.1, flex-2.5.31) generate code which is not consistent with the glibc provided by Arch (glibc-2.3.5). This can be experienced when compiling 'http://www.ballview.org/Downloads/Releases/BALL-1.1.tar.gz' on a stable Arch system.
The generated malloc declarations 'void* malloc(unsigned int)' differ from the /usr/include/stdlib.h declarations 'void* malloc(unsigned int) throw ()' of the same function. The difference being the 'throw()' at the end of the glibc declaration. The same goes for free(), too.
It seems SuSE 9 has the same problem and this is mentioned in the BALL FAQ at 'http://www.ball-project.org/Support/FAQ/FAQ.2005-01-08.0123'.
I did not manage to find out which versions of flex/bison work with glibc-2.3.5 but if you need any other information on this issue feel free to ask.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 21 June 2006, 19:51 GMT
Reason for closing:  Fixed
Additional comments about closing:  BALL compiles fine with gcc 4.1.1 and glibc 2.4, assuming this is fixed.

Loading...