Bug#258511: af: FTBFS with gcc-3.4: conflicting types for 'malloc'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Has any progress been made with this bug? Malc Arnold <[EMAIL PROTECTED]> wrote: > > What I don't get is that you *do* include the standard headers, but > > then you go and prototype their content *again*, by hand. This is > > obviously prone t

Bug#258511: af: FTBFS with gcc-3.4: conflicting types for 'malloc'

On 10 Jul, Roger Leigh wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Malc Arnold <[EMAIL PROTECTED]> writes: > > > On 09 Jul, Roger Leigh wrote: > >> > >> * It's written in K&R C. This has been obsolete for 16 years, and > >> must be converted. GCC will not support K&R forever

Bug#258511: af: FTBFS with gcc-3.4: conflicting types for 'malloc'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Malc Arnold <[EMAIL PROTECTED]> writes: > On 09 Jul, Roger Leigh wrote: >> >> * It's written in K&R C. This has been obsolete for 16 years, and >> must be converted. GCC will not support K&R forever; -traditional >> has already been removed. >

Bug#258511: af: FTBFS with gcc-3.4: conflicting types for 'malloc'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This patch does the minimum required to make af compile, but there are a number of serious problems with the source: * It's written in K&R C. This has been obsolete for 16 years, and must be converted. GCC will not support K&R forever; -tradi