On Wed, Mar 2, 2011 at 9:28 PM, Greg Comeau wrote:
> In article ,
> Fernan Bolando wrote:
>>just curious is it normal for 8l to follow some sort of precendence
>>based on the commandline? this being done through ape/pcc
>>
>>this is unable to build
>>8l -o spice -v /386/lib/ape/libf2c.a spice.8 u
> The --no-kvm-irqchip option on the command line may have solved the problem.
This apparently did not work with my host's setup. Same results observed when
I halted and rebooted this VPS this morning.
The host reports they are running KVM/qemu on Ubuntu Jaunty 9.04. I'm in
the process of setting
>and 8l will sort it out.
by which i meant: you then don't name any libraries at all,
since 8l will pick up the names from the references in the
include files. and therefore, as well as not having to name libf2c.a,
> you shouldn't need to mention libap.a,
the solution is to add
#pragma lib "/$M/lib/ape/libf2c.a"
to the include file that f2c's generated code uses,
and 8l will sort it out. you shouldn't need to mention libap.a,
either, since something should be including an ape include file
(and those have the #pragma libs)
In article ,
Fernan Bolando wrote:
>just curious is it normal for 8l to follow some sort of precendence
>based on the commandline? this being done through ape/pcc
>
>this is unable to build
>8l -o spice -v /386/lib/ape/libf2c.a spice.8 unix.8 /386/lib/ape/libap.a
>
>this was able to build
>8l -o s