At 09:37 AM 4/9/99 -0700, David O'Brien wrote:
The Only way I could get Jade to work with the new compiler
was with CFLAGS= -O -pipe
That is not so bad. Before EGCS, we would state that "-O" is the only
optimization that is know to always work and what we tell people to use.
Mike Smith has wr
At 09:58 AM 4/9/99 +0300, Maxim Sobolev wrote:
> Compile Jade with "-g" and see where in the coredump the signal 11 is
> occuring. What does ``ldd jade'' show? You might be mixing shared libs,
> that doesn't work for C++. Could also be an exceptions problem. Try
> compiling with -fnoexpcetion
> The Only way I could get Jade to work with the new compiler
> was with CFLAGS= -O -pipe
That is not so bad. Before EGCS, we would state that "-O" is the only
optimization that is know to always work and what we tell people to use.
Mike Smith has written about this many times in Hackers and Cur
> > Compile Jade with "-g" and see where in the coredump the signal 11 is
> > occuring.? What does ``ldd jade'' show?? You might be mixing shared libs,
> > that doesn't work for C++.? Could also be an exceptions problem.? Try
> > compiling with -fnoexpcetions.
>
> [asmo...@daemon] (163) $ ldd /usr/
On 08-Apr-99 David O'Brien wrote:
>> > Something broken in new egcs c++ compiler - jade doesn't work with
>> > following symptoms (checked on two machines).
>>
>> Apr 7 20:26:04 daemon /kernel: pid 61135 (jade), uid 0: exited on
>> signal
>> 11 (core dumped)
>>
>> Verified...
>>
>> David, might
> > Something broken in new egcs c++ compiler - jade doesn't work with
> > following symptoms (checked on two machines).
>
> Apr 7 20:26:04 daemon /kernel: pid 61135 (jade), uid 0: exited on signal
> 11 (core dumped)
>
> Verified...
>
> David, might this be due to the compiler itself of the lib
On 08-Apr-99 Maxim Sobolev wrote:
> Hi,
>
> While this problem might not belongs to this list however it is
> difficult in this case to distinguish exactly.
>
> Something broken in new egcs c++ compiler - jade doesn't work with
> following symptoms (checked on two machines).
Apr 7 20:26:04 daem
> eebsd.dsl -t sgml handbook.sgml
> *** Signal 11
>
> Interesting that when it was compiled using pgcc port it worked just
> fine.
Then it would probably do fine using the EGCS Port. But, the port !=
/usr/src. The library setup of EGCS in /usr/src is very different than
the Port
--
-- David
Hi,
While this problem might not belongs to this list however it is
difficult in this case to distinguish exactly.
Something broken in new egcs c++ compiler - jade doesn't work with
following symptoms (checked on two machines).
===> handbook
/usr/local/bin/jade -V html-manifest -ioutput.html? -c
