Path: utzoo!utgpu!watserv1!watmath!att!rutgers!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!sdd.hp.com!apollo!vasta
From: vasta@apollo.HP.COM (John Vasta)
Newsgroups: comp.sys.apollo
Subject: Re: Cross Compiling on the DN10,000
Message-ID: <4ba15618.20b6d@apollo.HP.COM>
Date: 16 Jul 90 19:54:00 GMT
References: <2316@dover.sps.mot.com>
Sender: root@apollo.HP.COM
Reply-To: vasta@apollo.HP.COM (John Vasta)
Followup-To: comp.sys.apollo
Organization: Hewlett-Packard Company, Apollo Division; Chelmsford, MA
Lines: 28

In article <2316@dover.sps.mot.com> turner@dover.sps.mot.com.UUCP (Robert Turner) writes:
>I'm using the DN10,000 as a compile engine.  I use the C compile
>flag -W0,cpu,3000 to force it to compile to the M68K class
>processors.
>
>Is it possible to also perform the "ld" on the DN10,000 for M68K
>class machines?

I would recommend using the -A cpu,3000 option instead of -W0. The
-A options are recognized by the /bin/cc driver, as opposed to the
-W0 options which are just passed through to the C compiler. If you
also use /bin/cc to perform the link step, then it will apply the
correct option to /bin/ld (i.e. any cpu setting implying a 68k
target causes "-A cpu,m68k" to be passed to ld). If you are calling
ld directly you can pass it "-A cpu,m68k" or "-A cpu,a88k" as well.
But since ld won't accept "-A cpu,3000" you can't automatically use
the same cpu option as that used during compilation. It's simpler
to let /bin/cc do the translation for you.

When ld sees a cpu option it will set the ISP environment variable
during its run so that library pathnames resolve to the correct
objects for that cpu type. As someone else pointed out, you must be
sure to have loaded the 68k *archive* libraries (e.g. those in
/usr/lib) on your DN10000.
John Vasta                Hewlett-Packard Apollo Systems Division
vasta@apollo.hp.com       M.S. CHA-01-LT
(508) 256-6600 x6362      300 Apollo Drive, Chelmsford, MA 01824
UUCP: {decwrl!decvax, mit-eddie, attunix}!apollo!vasta