Hi Srirama
Even I had the problem of this "workspace not found" error when I was in
bldenv environment.
So, I ran webrev command without running "env - bldenv
./sfw-developer.sh". And hence webrev -O command worked for me.
Thanks
Spoorthy
Srirama Sharma wrote:
> Hi,
>
> Jim Walker said the following on Wednesday 18 February 2009 11:38 PM:
>> Spoorthy,
>>
>> mogo.sfbay:/builds/ss224839/
>> -bash-3.2$ ws `pwd`
>> -bash: ws: command not found
>> -bash-3.2$
>> PATH=/ws/onnv-tools/onbld/bin:/ws/onnv-tools/teamware/bin:$PATH
>> -bash-3.2$ ws `pwd`
>> /ws/onnv-tools/onbld/bin/ws[300]:
>> /builds1/ss224839/Codemgr_wsdata/sunos/protodefs: not found
>>
>> Something is wackey. How did this builds1 reference get
>> into your builds directory?
>
> I had faced this problem before.
>
> The reason for this problem is bldenv script resets your PATH variable.
>
> <excerpt from /opt/onbld/bin/bldenv script>
> 401 # Set PATH for a build
> 402
> PATH="/opt/onbld/bin:/opt/onbld/bin/${MACH}:/opt/SUNWspro/bin:/usr/ccs/bin:/usr/bin:/usr/sbin:/usr/ucb:/usr/etc:/usr/open
>
>
> win/bin:/usr/sfw/bin:/opt/sfw/bin:."
> 403 if [[ "${SUNWSPRO}" != "" ]]; then
> 404 export PATH="${SUNWSPRO}/bin:$PATH"
> 405 fi
> ......
> 431 PATH="${TOOLS_PROTO}/opt/onbld/bin/${MACH}:${PATH}"
> 432 PATH="${TOOLS_PROTO}/opt/onbld/bin:${PATH}"
> 433 export PATH
>
> So even if you had the teamware dir (i.e /ws/onnv-tools/teamware/bin)
> in your PATH variable, that will get reset after running bldenv. Hence
> any wx / ws commands complain that 'workspace' is not found in PATH.
>
> The workaround I use is to add the teamware dir to PATH variable after
> running the bldenv script as shown below
>
> bash-3.2$ /opt/onbld/bin/bldenv sfw-developer.sh
> bash-3.2$ export PATH=$PATH:/ws/onnv-tools/teamware/bin:
>
> But make sure you undo these changes before starting a nightly so that
> 'cc' in /ws/onnv-tools/teamware/bin dir doesn't cause any problem.
>
> HTH.
>
> Thanks,
> Srirama
>
