can't build bjam

Hi !

I've checked out the RC_1_34_0 branch add tried to compile
bjam using cygwin 
bash.
The compile fails with:

./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root=
clean
assertion "!strcmp( l->string,
"c:\\foo\\bar" )" failed: file
"expand.c", line 
714

(full output attached).

It seems this is the mysterious path issue again.

Any Ideas ? 
What information do you need to debug this ?

Yours,

Jürgen

-- 
* Dipl.-Math. Jürgen Hunold  ! Ingenieurgesellschaft für 
* voice: ++49 511 262926 57  ! Verkehrs- und Eisenbahnwesen
mbH  
* fax  : ++49 511 262926 99  ! Lister Straße 15
* hunoldive-mbh.de          ! www.ive-mbh.de
###
### Using 'gcc' toolset.
###
rm -rf bootstrap
mkdir bootstrap
gcc -o bootstrap/jam0 command.c compile.c debug.c execunix.c
expand.c fileunix.c glob.c hash.c hdrmacro.c headers.c jam.c
jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c
parse.c pathunix.c pathvms.c regexp.c rules.c scan.c
search.c subst.c timestamp.c variable.c modules.c strings.c
filesys.c builtins.c pwd.c class.c native.c w32_getreg.c
modules/set.c modules/path.c modules/regex.c
modules/property-set.c modules/sequence.c modules/order.c
execnt.c filent.c
./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root=
clean
assertion "!strcmp( l->string,
"c:\\foo\\bar" )" failed: file
"expand.c", line 714
./build.sh: line 13:  1264 Aborted                 (core
dumped) $
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Jürgen Hunold wrote:
> Hi !
> 
> I've checked out the RC_1_34_0 branch add tried to
compile bjam using cygwin 
> bash.
> The compile fails with:
> 
> ./bootstrap/jam0 -f build.jam --toolset=gcc
--toolset-root= clean
> assertion "!strcmp( l->string,
"c:\\foo\\bar" )" failed: file
"expand.c", line 
> 714
> 
> (full output attached).
> 
> It seems this is the mysterious path issue again.

Grrr :-(

> Any Ideas ? 

Not really.

> What information do you need to debug this ?

Hm, I think the only info would be what this code.. does for
your cygwin 
install...

     char cygpath[256];
    
cygwin_conv_to_posix_path("c:\\foo\\bar",
cygpath);

The key info is the value of "cygpath". The
above is part of the 
var_expand_unit_test function in expand.c. So perhaps you
can run the 
jam0.exe in GDB, set a break point at the above point, and
see what happens.

Unfortunately the docs on cygwin_conv_to_posix_path are
rather slim 
<http://www.cygwin.com/cygwin-api/func-cy
gwin-conv-to-posix-path.html> 
so using it is a hit and miss effort.


-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software
.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

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

Hi Rene !

On Wednesday 29 March 2006 19:13, Rene Rivera wrote:
> Jürgen Hunold wrote:
> > It seems this is the mysterious path issue again.
>
> Grrr :-(

Exactly.

> Hm, I think the only info would be what this code..
does for your
> cygwin install...
>
>      char cygpath[256];
>     
cygwin_conv_to_posix_path("c:\\foo\\bar",
cygpath);
>
> The key info is the value of "cygpath". The
above is part of the
> var_expand_unit_test function in expand.c. So perhaps
you can run the
> jam0.exe in GDB, set a break point at the above point,
and see what
> happens.

I'll give it try tomorrow morning. It will be the first
time I use gdb 
on cygwin, so don't expect too much from me )
Or I add a simple printf statement, which should give the
needed answer 
too.

> Unfortunately the docs on cygwin_conv_to_posix_path are
rather slim
> <http://www.cygwin.com/cygwin-api/func-cygwin
-conv-to-posix-path.html
>> so using it is a hit and miss effort.

Wow. Thats _really_ short. And there are no source
available, I guess ?

Yours,

Jürgen

-- 
* Dipl.-Math. Jürgen Hunold  ! Ingenieurgesellschaft für 
* voice: ++49 511 262926 57  ! Verkehrs- und Eisenbahnwesen
mbH  
* fax  : ++49 511 262926 99  ! Lister Straße 15
* hunoldive-mbh.de          ! www.ive-mbh.de
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Hi Rene !

Am Middeweken 29 März 2006, 19:42 schrieb Juergen Hunold:

> > Hm, I think the only info would be what this
code.. does for your
> > cygwin install...
> >
> >      char cygpath[256];
> >     
cygwin_conv_to_posix_path("c:\\foo\\bar",
cygpath);
> >
> > The key info is the value of
"cygpath". The above is part of the
> > var_expand_unit_test function in expand.c. So
perhaps you can run the
> > jam0.exe in GDB, set a break point at the above
point, and see what
> > happens.

gdb is hard for someone who is used to have log files, debug
messages and 
kdbg )

So I've put in some printfs just before the assert (see
diff) and get (see 
debug.txt):

/c/foo/bar for cygpath.

Does this help ?

Yours,

Jürgen
-- 
* Dipl.-Math. Jürgen Hunold  ! Ingenieurgesellschaft für 
* voice: ++49 511 262926 57  ! Verkehrs- und Eisenbahnwesen
mbH  
* fax  : ++49 511 262926 99  ! Lister Straße 15
* hunoldive-mbh.de          ! www.ive-mbh.de
###
### Using 'gcc' toolset.
###
rm -rf bootstrap
mkdir bootstrap
gcc -o bootstrap/jam0 command.c compile.c debug.c execunix.c
expand.c fileunix.c glob.c hash.c hdrmacro.c headers.c jam.c
jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c
parse.c pathunix.c pathvms.c regexp.c rules.c scan.c
search.c subst.c timestamp.c variable.c modules.c strings.c
filesys.c builtins.c pwd.c class.c native.c w32_getreg.c
modules/set.c modules/path.c modules/regex.c
modules/property-set.c modules/sequence.c modules/order.c
execnt.c filent.c
./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root=
clean
assertion "!strcmp( l->string,
"c:\\foo\\bar" )" failed: file
"expand.c", line 716
C:\foo\bar
/c/foo/bar
./build.sh: line 13:  3752 Aborted                 (core
dumped) $
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build