Boost logo

Boost-Build :

From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-03-25 12:04:27

On 2002-03-25 at 08:58 AM, gohmandj_at_[hidden] (Dan Gohman) wrote:

>I'm working on othoganalizing (?) my ABI/ISA changes, and I'm running into
>errors that I don't know how to interpret.
>I added these to features.jam:
>feature sgi-abi : n32 n64 ;
>feature sgi-isa : mips3 mips4 ;
>and made the appropriate changes to mipspro-tools.jam, but when I try
>do a build where I specify both the ABI and a non-default ISA, it doesn't
>-sBUILD="<sgi-abi>n64 <sgi-isa>mips4"
>required property <sgi-abi>n32 incompatible with <sgi-abi>n64
>-sBUILD="<sgi-abi>n32 <sgi-isa>mips4"
>required property <sgi-isa>mips3 incompatible with <sgi-isa>mips4
>required property <sgi-abi>n32 incompatible with <sgi-abi><sgi-isa>mips4
>If I specify mips4 and leave off the ABI, it works using the default ABI
>(-sBUILD="<sgi-isa>mips4"). I've experimented with several other
>variations, only to get similar errors. Is there a way to use more than
>one feature like this, or am I looking at a bug? I'm using the v1 build
>system; is this something worth trying with the v2 build system?

I think adding: <sgi-abi> <sgi-isa>, to the gLINK_COMPATIBLE variable in
features.jam will do the trick.

-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at