From: David Abrahams (dave_at_[hidden])
Date: 2003-12-12 13:28:40
"Olden A (Comp)" <aolden_at_[hidden]> writes:
>>>What was the problem with the set command?
> I'm not sure yet - I am trying to find, because it's all software that does
> this, not just boost - but up until it hasn't been a problem (or even
> noticeable) - when I find out I will let you now, although I'm getting vibes
> that it is something in my path that's causing it, because SET
> CLASSPATH=%CLASSPATH% works just fine
>>> I tracked it down to GNUWIN32. I'm not sure how but the path entry became
> managled to "C:|GNUWIN32\bin", rather than "C:\GNUWIN32", so the set command
> was failing there.
Ah, that *would* cause problems. I wonder if we need to change it to
something more like:
Could you try that out (with the old C:|GNUWIN32\bin entry) and let
me know what happens?
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk