[Info-vax] cross tools and CLD scope

[Craig A. Berry]

On 10/18/21 4:41 AM, hb wrote:
> On 10/18/21 4:06 AM, Robert A. Brooks wrote:
>> On 10/17/2021 8:56 PM, Bob Wilson wrote:
>>> I don't know if this will solve your problem (I'm not familiar with
>>> MMK), but
>>> for MMS we use the .FIRST directive to run a command procedure which,
>>> among
>>> other things, runs a setup command procedure for "tools" (worked fine
>>> in the
>>> IA64 port, haven't tried it yet for x86)
>>
>> Using the .FIRST directive in MMS works with the IA64-based X86
>> cross-tools compilers.

Thanks for all the replies.  Yes, .FIRST works for simple cases and when
MMS or MMK is the thing spawning the compile command.

> Yes, command tables are not propagated to spawned subprocesses. This
> affects MMS/MMK.

And anything else that does a compile or link in a subprocess.

> As mentioned, there is a .FIRST for MMS/MMK, you should have the cross
> tools setup in the .FIRST. If you don't want to change the existing
> makefile, ahem description file, you can concatenate a "first" file with
> your existing one: /DESCRIPTION=("DESCRIP+FIRST"). Yes, quoted. This
> works for MMS. I can't get that to work for MMK. Here you may need
> something like "$ pipe type/noheader descrip.mms+first.mms |
> mmk/descr=sys$pipe". For MMS there can be only one first in the
> concatenated description. That explains my order of the plus list. The
> last one wins. For MMK you can have several, all seem to be executed. If
> you use MMS and already have a .FIRST in your DESCRIP.MMS, you may need
> to copy the actions from that to the "first" description file.

That's all impressive and scary.  Luckily editing .FIRST or the code
that generates it to include the cross tools set-up got me as far as I
can get with that mechanism.  Then I was on to cases where code is
generated that needs to be compiled and run natively to probe for
features that will then be used to generate additional code that will
need to be built with the cross tools.  It's not going to be pretty.
But the weekend is over and I'm back to doing real work :-(.