From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-03-25 12:42:54
----- Original Message -----
From: "Rene Rivera" <grafik666_at_[hidden]>
Sent: Monday, March 25, 2002 12:04 PM
Subject: Re: [jamboost] Re: [boost] more SGI build updates
> 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
> >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 ;
I think these might as well live in the sgi toolset.
> >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
> >-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
The slash notation is currently used to get two different values of a
single feature. Legal usage would be:
> >If I specify mips4 and leave off the ABI, it works using the default
> >(-sBUILD="<sgi-isa>mips4"). I've experimented with several other
> >variations, only to get similar errors. Is there a way to use more
> >one feature like this, or am I looking at a bug?
Seems bug-ish to me.
> I'm using the v1 build
> >system; is this something worth trying with the v2 build system?
That's not fully implemented yet; you wouldn't stand a chance :-(
> I think adding: <sgi-abi> <sgi-isa>, to the gLINK_COMPATIBLE variable
> features.jam will do the trick.
Are the different values of <sgi-abi> link-compatible with one another?
I don't think so!
That sounds dangerous to me.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk