Richard writes:
> We have successfully installed the GNU c compiler (gcc 2.95.2) on one of
> our test MPE/iX machines (MPE_IX C.60.02).

Good:

>
> file:test.c
> ----------------------------------
>
> #pragma intrinsic HPGETPROCPLABEL

Note that GCC's C does not implement #pragma intrinsic at the moment, so
there will be some additional complexities required to call Intrinsics so
that parameters get passed correctly.

> /usr/local/bin/gcc gcc -c test.c will produce test.o will have a BLANK
> code

This is normal, and except for one particular LINKEDIT verison it should not
cause any problems.  You may get a warning about the vile not having an
NMOBJ file code, but it will still work.

> /usr/local/bin/gcc gcc -c test.c will produce a.out as a NMPRG
> ( I understand that this prog would not normally execute as it is - no
> main()- I was just giving it a try.)

Yes, that should work fine.

> :file xyz=./test.o
>
> attempting to use LINKEDIT to build an XL,
> on test.o
> EXPECTED FILECODE NMRL FOR FILE "*XYZ"  (LINKERR 1124)
> 0 OBJECT FILES HAVE BEEN ADDED.

For these examples can you provide the linkedit command that you're trying?

Generally when using gcc it's easier to work in the Posix domain and use the
'gcc' command to both create your .o files *and* produce a shared library
(i.e. an XL file) rather than trying to do it manually with LINKEDIT, since
gcc knows about various libraries that may be required, etc.

> :file *xyz=./a.out
> on a.out
> EXPECTED FILECODE NMRL FOR FILE "*XYZ"  (LINKERR 1124)

You can't add a program file to an XL.

G.

www.gccsupport.com

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *