dg/ux port issues

[Zack Weinberg]

Takis Psarogiannakopoulos wrote:
> 
> Folks,
> I am not sending that to the list since there is
> no reason to overwhelm it with endless messages.

Please don't do this.  Keep discussion on the list.  I don't know
everything. 

> To:Jeffrey A Law:
> Eric Raskin was working (as you probably know)
> with egcs-1.1.2. He was trying to fix the dwarf-2.
> The dtl program of DG/ux is buggy. That is the main
> reason that gcc can not produce dwarf-2 debug in DG/ux.
> DG refuse to fix it... Good or bad DGUX has its own ways.
> I am not going to after DG to do that and this.

This has nothing to do with cpp...

> libgcc.a is being accessed also from elink. 

It should not be necessary.  If you cannot link a program with gcc,
that is a bug in the specs, which needs to be fixed.  Your example:

> link as : 
>           -lgcc -lthread -lc !!! (using ld and not gcc)
> If --prefix was /usr/sde/ix86dgux/usr/lib I could nt see clearly 
> the libgcc.a.

has something deeply wrong with it.  libgcc should have no
dependencies on libc, for one thing.

> What we looking here is just a simple rule in the gcc/Makefile
> possible to compile a complete cpp (and not in two parts),
> as it was in 2.8.1. It can be only for DG/ux. 

We will not do this.

Leave the internal cpp in lib/gcc-lib/whatever/2.95/cpp.  Put bin/cpp
in the elink directory.  If that doesn't work, please explain what
goes wrong with it in excruciating detail, and maybe we can fix it.

> >
> > What are the missing features of the "external cpp" as you call it?
> >
> 
> I cannt remember since I switced back to gcc-2.8.1 I will build
> tonight a gcc-2.95 and then an XFree86-3.3.5 I and will get back to 
> you.

Ok.

zw