[reSIProcate] Resiprocate 0.9.0 -- Released

[Nils Ohlmeier]

Hi Leonardo,

On Monday 11 July 2005 16:28, Leonardo N. S. Pereira wrote:
> I downloaded resiprocate-0.9.0-5019
> I build whith:
> #./configure
> #make
>
> And than:
>
>  g++ -DHAVE_CONFIG_H -I. -I. -I. -I.. -I..
> -I/tmp/resiprocate-0.9.0-5019/contrib/ares -I/usr/kerberos/include -g
> -O2 -Wall -Wno-deprecated -MT QuotedDataParameter.lo -MD -MP -MF
> .deps/QuotedDataParameter.Tpo -c QuotedDataParameter.cxx  -fPIC -DPIC -o
> .libs/QuotedDataParameter.o
> QuotedDataParameter.cxx: In constructor
> `resip::QuotedDataParameter::QuotedDataParameter(resip::ParameterTypes::Typ
>e, resip::ParseBuffer&, const char*)':
> QuotedDataParameter.cxx:30: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:https://qa.mandrakesoft.com/> for instructions.
> make[3]: *** [QuotedDataParameter.lo] Error 1
> make[3]: Leaving directory `/tmp/resiprocate-0.9.0-5019/resiprocate'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/tmp/resiprocate-0.9.0-5019/resiprocate'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/tmp/resiprocate-0.9.0-5019/resiprocate'
> make: *** [all-recursive] Error 1
> /
>
> Do someone know what happned??
> I'm using Linux whith kernel 2.6.11.7 and glibc-2.3.3.

AFAIK compiler seg faults are typically not caused by the compiled code 
itself. In most cases it is a hint for errors in the environment, like bad 
cooling of the CPU, memory which runs to fast, etc.
Dont get me wrong, but did you already made big compile jobs (like endless 
compiling of the kernel) successfull on that machine?

Regards
  Nils