Btw if I change gcc.jam on line 141:

       }
       flags gcc.link RUN_PATH $(condition) : $(lib_path) ;
   }

to:

       }
       ECHO Notice: hack for bjam on bash 3.2.3
       flags gcc.link RUN_PATH $(condition) : $(lib_path) ;
   }

All test run - the output is:

dolly@star:~/my_test$ bjam --without-python --toolset=gcc
Notice: hack for bjam on bash 3.2.3 flags gcc.link RUN_PATH <toolset>gcc-4.1.2
Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(don't panic: this is a strictly optional feature).
...patience...
...patience...
...found 2118 targets...

<...>

Running 2 test cases...

*** No errors detected

Is there a proper fix for this?

Regards,

Dirk

Dirk Griffioen wrote:

Hi All,

I get a strange error at the end of my unit-tests on ubuntu 7.04, gcc 4.1.2, bash 3.2.13 and bjam 3.1.14 (boost.build v2 milestone 14), after which the build says 'failed'

': bad variable nameRY_PATH '

same version of bjam, but an older bash (2.5):

warning: ': not a valid identifier`LD_LIBRARY_PATH

Does anyone know what is wrong here (and how to fix it :) ?

It's not: rights, comanndline length, environment -- I think I got the obvious ... Can somebody please help?

Regards,

Dirk
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
  

-- 
CodeShop BV

www.code-shop.com
+31 6 411 92 024