hmm, nothing is jumping out at me. Can you please also add a bit more information to bjam's output as follows: c:\boost\boost_1_38_0\bjam.exe -d2 --toolset=msvc
-greg On Fri, May 29, 2009 at 9:39 PM, Peter Harley <[email protected]> wrote: > Hi, > > Greg Landrum wrote: >> >> Needless to say, I haven't seen this happen. Let's try and track it down. >> > > Shame, I was hoping it was something obvious I'd forgotten to do! >> >> Some questions: >> - If you repeat the build command, does it stop in the same place? >> - Please send the command you are using to do the build and the values >> of the relevant environment variables. >> >> -greg >> > > I've tried building several times now, always with the same configuration, > but it always stops there. > > This is what happens if I interupt the compile and try and start it again, > it also contains the information you asked for: > > C:\RDKit\Code>c:\boost\boost_1_38_0\bjam.exe --toolset=msvc > ...patience... > ...patience... > ...patience... > ...found 10075 targets... > ...updating 678 targets... > ...interrupted > ^C > C:\RDKit\Code>echo %PATH5 > %PATH5 > > C:\RDKit\Code>echo %PATH% > C:\MDL\DiscoveryGate\Hop-Into;C:\Program Files\PC Connectivity > Solution\;C:\WIND > OWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program > Files\GnuWin32\bin;C > :\Python25;C:\RDKit\bin;C:\boost\lib > > C:\RDKit\Code>echo %RDBASE% > c:\RDKit > > C:\RDKit\Code>echo %BOOSTHOME% > c:\boost\boost_1_38_0 > > C:\RDKit\Code>echo %BOOST_BUILD_PATH% > c:\boost\boost_1_38_0 > > Thanks again, > > Pete >
