Re: BUG intel toolset causes ambiguity in named prebuild library

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: BUG intel toolset causes ambiguity in named prebuild library

Daniel Einspanjer
I'm getting a similar error when trying to source a <file> using the
intel-linux toolset.

Is there any chance the line in intel-linux.jam:
    generators.override builtin.lib-generator : intel-linux.prebuilt ;
should be
    generators.override builtin.prebuilt : intel-linux.prebuilt ;
instead?

I did try making that change and it fixed my error, but I honestly don't
know enough about the system yet to know if I will blow up down the road
because of it.

Daniel

"Vladimir Prus" <[hidden email]> wrote in message
news:[hidden email]...

> Hi Michael,
>
>> Just stumbled across a fairly recently introduced bug. The latest HEAD
>> has
>> problems with the following simple test case.
>>
>> lib lapack2 : : <name>lapackD <variant>debug : : ;
>> lib lapack2 : : <name>lapackR <variant>release : : ;
>>
>>
>> This is fine in itself. The problem only crops up when the 'intel'
>> toolset
>> is used. i.e.
>> bjam intel
>>
>> Fails with the error
>>  generators.jam:1079: in construct-really from module generators
>> error: Ambiguity found when searching for best transformation
>
> Yea. (Hint: if you get error in generators.jam, the --debug-generators
> option
> can provide interesting information).
>
> The reason for this error is that there are two generators that can handle
> the
> above. First is fully generic generator that just produces a target.
> Second
> is a generator intel-linux.searched-lib-generator that has some additional
> logic (having to do with library order of link line).
>
> Until recently, both generators were run. But they produced the same
> targets,
> so no ambiguity ware reported. I've recently changed the check so that
> whenever two generators can be run and both produce something, it's an
> error.
> That's what you see.
>
> I've just committed a patch that uses generators.override rule to specify
> that
> intel-linux.searched-lib-generator should be preferred over generic
> searched-lib-generator in all cases, so now only one generator is run, and
> everything should be OK. And I think it's a bit faster (tiny bit, but
> anyway).
>
> Thanks for the report!
>
> - Volodya
>
> --
> Vladimir Prus
> http://vladimir_prus.blogspot.com
> Boost.Build V2: http://boost.org/boost-build2
>
>
>
> Yahoo! Groups Links
>
> <*> To visit your group on the web, go to:
>    http://groups.yahoo.com/group/jamboost/
>
> <*> To unsubscribe from this group, send an email to:
>    [hidden email]
>
> <*> Your use of Yahoo! Groups is subject to:
>    http://docs.yahoo.com/info/terms/
>
>
>
>



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build