Mark (the "other Mark") writes about porting to the 3000:

>Major C packages are all pretty much similar -- some sort of configure step
>which generates a Makefile which describes how all of the pieces of the
>package are compiled and linked together.  Generally you just do a "make"
>which reads the Makefile to learn how to invoke the compiler(s)
>automatically.

Agreed. However, if anything uses the GNU Autoconfigure stuff, a slight
modification to the ./configure script is in order. The ./configure
script usually tries to get a flavor for the target machine by compiling
a bunch of small test programs. It does static linking and relies on the
linkeditor to complain if libraries aren't supported. On MPE since by
definition, there is no static linking, a bunch of things could get
missed by this technique without a slight modification.

Edit the ./configure script and look for the line containing $ac_link.
It will usually look something like:

ac_link='${CC-cc} $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext -o \
conftest $LIBS 1>&5 2>&5'

Modify this to:

ac_link='${CC-cc} $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext -o \
conftest $LIBS 1>&5 2>&5 && ./conftest 1>&5 2>&5'

Invoke it, and you're off and running!


Regards,


GNU Mark