como build problems
Some time ago my bjam/comeau set up ceased to function. I get messages like: C++ prelinker: executing: c:\Program Files\como433\bin\como --vc71 -e5 --no_vers ion --no_prelink_verbose --display_error_number --long_long --diag_suppress= 9,21 ,161,748,940,962 -D__STL_LONG_LONG -DNDEBUG -DNDEBUG -DBOOST_LIB_DIAGNOSTIC= 1 -- a -DBOOST_COMO_STRICT=1 --inlining -D_WIN32 -DBOOST_SP_DISABLE_THREADS --exc epti ons -DBOOST_DISABLE_WIN32 --wchar_t -I..\..\..\bin\boost\libs\serialization\ buil d -Ic:\Program Files\como433\libcomo c:\Program Files\como433\libcomo\cnames -IC :\BoostMainCVS -IC:\BoostMainCVS -IC:\BoostMainCVS -o ..\..\..\bin\boost\libs\se rialization\build\libboost_serialization.lib\como-4_3_3-vc7_1\release\binary _oar chive.obj -c ../src/binary_oarchive.cpp 'c:\Program' is not recognized as an internal or external command, operable program or batch file. My como path variable is set: COMO_PATH="c:\\Program Files\\como433" I also tried COMO_PATH="c:/Program Files/como433" but it made no differenc I didn't change anything as far as I know. Does anyone have any suggestions? Robert Ramey
Robert Ramey wrote:
Some time ago my bjam/comeau set up ceased to function.
I get messages like:
<snip>
'c:\Program' is not recognized as an internal or external command, operable program or batch file.
My como path variable is set:
COMO_PATH="c:\\Program Files\\como433"
I also tried
COMO_PATH="c:/Program Files/como433"
but it made no differenc
I didn't change anything as far as I know. Does anyone have any suggestions?
I was not able to get como to work correctly until I installed it in a path containing no space characters and moved all my libraries, including Boost, to such a path. Now it works more or less okay.
Robert Ramey
Jonathan
----- Original Message ----- From: "Jonathan Turkanis" <technews@kangaroologic.com> To: <boost@lists.boost.org> Sent: Sunday, June 19, 2005 12:40 AM Subject: Re: [boost] como build problems
Robert Ramey wrote:
Some time ago my bjam/comeau set up ceased to function.
I get messages like:
<snip>
'c:\Program' is not recognized as an internal or external command, operable program or batch file.
My como path variable is set:
COMO_PATH="c:\\Program Files\\como433"
I also tried
COMO_PATH="c:/Program Files/como433"
but it made no differenc
I didn't change anything as far as I know. Does anyone have any suggestions?
I was not able to get como to work correctly until I installed it in a path containing no space characters and moved all my libraries, including Boost, to such a path. Now it works more or less okay.
Before moving everything to a new folder, perhaps you could try using the alternative spelling for DOS compatibility: COMO_PATH="C:/PROGRA~1/COMO433" Christopher Diggins http://www.cdiggins.com
christopher diggins wrote:
Before moving everything to a new folder, perhaps you could try using the alternative spelling for DOS compatibility:
COMO_PATH="C:/PROGRA~1/COMO433"
Unfortunately, I tried that an it didn't work. I even rewrote everything in my PATH enviroment variable -- since some of como's error messages seemed to contain fragments of directories in my PATH -- with no luck. Jonathan
christopher diggins <cdiggins@videotron.ca> writes:
Before moving everything to a new folder, perhaps you could try using the alternative spelling for DOS compatibility:
COMO_PATH="C:/PROGRA~1/COMO433"
Try this one instead: COMO_PATH="\"C:/Program Files/como433\"" -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams wrote:
christopher diggins <cdiggins@videotron.ca> writes:
Before moving everything to a new folder, perhaps you could try using the alternative spelling for DOS compatibility:
COMO_PATH="C:/PROGRA~1/COMO433"
Try this one instead:
COMO_PATH="\"C:/Program Files/como433\""
What's the pattern here? I don't get it. Jonathan
Jonathan Turkanis wrote:
David Abrahams wrote:
christopher diggins <cdiggins@videotron.ca> writes:
Before moving everything to a new folder, perhaps you could try using the alternative spelling for DOS compatibility:
COMO_PATH="C:/PROGRA~1/COMO433"
Try this one instead:
COMO_PATH="\"C:/Program Files/como433\""
What's the pattern here? I don't get it.
The pattern is to enclose a path which has spaces in an extra set of quotation marks.
Edward Diener wrote:
Try this one instead:
COMO_PATH="\"C:/Program Files/como433\""
What's the pattern here? I don't get it.
The pattern is to enclose a path which has spaces in an extra set of quotation marks.
Thanks; somehow I didn't see the quotation marks. I read it as \C:/Program Files/como433\ Jonathan
Didn't work for me. I have very odd behavior. When try to build he library with bjam -sTOOLS=como-4_3_3-vc7_1 >bjam.log I get the problem cited above and the build seems to stop working. Then I do it again and it occurs with a different module and build halts. Each time I attempt, the build fails to build the library for lack of some required object modules. I suspect that might be only my problem. On the other hand, I had to change the command line in my como batch file that I use for non-bjam builds as it seems the required command line settngs changes. Robert Ramey David Abrahams wrote:
christopher diggins <cdiggins@videotron.ca> writes:
Before moving everything to a new folder, perhaps you could try using the alternative spelling for DOS compatibility:
COMO_PATH="C:/PROGRA~1/COMO433"
Try this one instead:
COMO_PATH="\"C:/Program Files/como433\""
"Robert Ramey" <ramey@rrsd.com> writes:
Didn't work for me.
I have very odd behavior. When try to build he library with
bjam -sTOOLS=como-4_3_3-vc7_1 >bjam.log
I get the problem cited above and the build seems to stop working. Then I do it again and it occurs with a different module and build halts. Each time I attempt, the build fails to build the library for lack of some required object modules.
It might be a good idea to delete any files called ".jamdeps" that you can find.
I suspect that might be only my problem.
But that's not "the problem cited above" AFAICT. You were talking about mangled command-lines, weren't you?
On the other hand, I had to change the command line in my como batch file that I use for non-bjam builds as it seems the required command line settngs changes.
Please do bjam -a -sTOOLS=como-4_3_3-vc7_1 -obuild.dump and look at the resulting build.dump file. You should be able to see every command that's issued, and pick out the problems. If there are problems in the command lines, please post the entire file. -- Dave Abrahams Boost Consulting www.boost-consulting.com
Robert Ramey wrote:
Some time ago my bjam/comeau set up ceased to function.
Should be fixed now, in CVS. By some time ago you mean August of last year? Because that's the most recent change I can see affecting this functionality. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
Actually, I meant in the last month or two. Robert Ramey Rene Rivera wrote:
Robert Ramey wrote:
Some time ago my bjam/comeau set up ceased to function.
Should be fixed now, in CVS. By some time ago you mean August of last year? Because that's the most recent change I can see affecting this functionality.
participants (6)
-
christopher diggins -
David Abrahams -
Edward Diener -
Jonathan Turkanis -
Rene Rivera -
Robert Ramey