RE: gcc 4.5.0 libiberty .o vs. .obj confusion

[Jay K <jay dot krell at cornell dot edu>]

> CC: gcc@
> From: iant@
>
> Jay:
>> I'm guessing that every ".o" in libiberty/Makefile.in should be changed to $(OBJEXT).
>
> Yes.
>
> Ian

Thanks. 

Specifically ".o" goes to ".@OBJEXT@".

There's no way I'm going to be able to get "the papers" in.
I can try to squeak by via triviality of change.
I'm slightly derailed on other aspects of targeting VMS (e.g. *crt0*.c, vms-crtl.h), but this did work for me, attached.
It's many lines, but highly mechanical.
There are a few places where ".o" occurs in comments, can be left alone.
There is:

.c.o:
??? false

> .c.obj:
>??? false


and
<??? -rm -rf *.o pic core errs \#* *.E a.out

>??? -rm -rf *.o *.obj pic core errs \#* *.E a.out


and I wrapped the affected lines to one file per line, and spaces instead of tabs (consistent rendering)


?- Jay

Attachment: libiberty-vms-o-vs-obj.txt
Description: Text document