[Php-java-bridge-users] Bug in gcc optimizer (was: Re: failed to install in FreeBSD)

Hi,

> It is ok now..

if i remember correctly, this gcc optimizer bug is due
to an uninitialized condition variable. Depending on
what malloc() returns, the gcc optimizer creates trash
output. When you compile twice, it is more likely that
malloc() returns a segment which initializes the
variable to zero.


> Maybe yesterday package is wrong.

I don't think so. The bind code hasn't been changed
since one year now.


Regards,
Jost Boekemeier



      __________________________________  Yahoo! Clever: Sie haben Fragen? Yahoo! Nutzer antworten Ihnen. www.yahoo.de/clever