Richard Lowe <> wrote:
> Aubrey Li wrote:
>> Richard Lowe <> wrote:
>>> Aubrey Li wrote:
>>>> Hi,
>>>>
>>>> I run into this error when I tried to build b136.
>>>>
>>>> ==============================================
>>>> aubrey at wsmep:~/work/onnv-b136/usr/src/tools$ dmake install
>>>> ----snip----
>>>> sh: line 1:
>>>> /export/home/aubrey/work/onnv-b136/usr/src/tools/proto/opt/onbld/bin/i386/cw:
>>>> not found
>>>> ==============================================
>>>>
>>>> I must miss some changes notification recently, but I wonder why we
>>>> did this change.
>>>
>>> The tools proto path not containing ${MACH} made various things more
>>> annoying than they should be [1]. ?The change you missed is the
>>> requirement to use current tools, including nightly, after the
>>> integration of on_ips.
>>>
>>
>> Where can I get the current tools?
>
> I don't know the answer to that, I normally build them locally rather
> than downloading them. ?I would hope that the b136 drop will contain a
> tarball, but I'm not certain.
>
>> I didn't use nightly at this moment. I just copy the opensolaris.sh from
>> ./usr/src/tools/env and did "dmake install" under ./usr/src/tools.
>> This is what I did previously, is this changed? What I did wrong?
>
> The same applies to bldenv, which I assume you're using, sorry I didn't
> mention that.
>
> The easiest way around this is probably 'make' in usr/src/tools/scripts,
> and to copy the resulting nightly and bldenv somewhere and use them.
> Once you've crossed the flag day this way, you could build a
> developer/build/onbld package from your workspace.
This works.
So, do you have another around to get the current close bin file? :)
Thanks,
-Aubrey
>
>> Do we have the change documented somewhere?
>
> http://static.opensolaris.org/on/flagdays/pages/20100302184109.html
> http://static.opensolaris.org/on/flagdays/pages/20100303235050.html
>
> -- Rich
>
