To answer my own question, I backed out changes that were made to jam_src/expand.c since the last "stable" build to work around this problem.  The changes were for unit testing and don't jive with cygwin.

The value of the string l->string at the point of failure, at:

assertion "!strcmp( l->string, "c:\\foo\\bar" )" failed: file "expand.c", line 723

is "C:\\cygwin\\usr\\c\\foo\\bar".  Back to the drawing board.  :-)

Cheers,
Mark

Mark Evans <evans_mark@yahoo.com> wrote:

Has there been any progress on this issue?  I am getting this assertion failure with the latest nightly build on CYGWIN which was installed using the default /cygdrive/c .  Can I edit out the assertion as a workaround or what?

Regards,
Mark

Rene Rivera <grafik.list@redshift-software.com> wrote:

John Maddock wrote:
> An assertion fails when trying to build with cygwin gcc, anyone any ideas?
>
> assertion "!strcmp( l->string, "c:\\foo\\bar" )" failed: file "expand.c",

Yes! :-)

There's code in the var_expand_unit_test that tries to verify the
functionality of expanding paths. In the case of Cygwin it wants to
check that something like "/cygdrive/c/foo/bar" is translated to
something like "c:\foo\bar". The problem comes in that the "/cygdrive"
part is a user configurable path on Cygwin. I wrote code that tries to
decipher what that 'cygdrive' is, as there doesn't seem to be any Cygwin
call to get that value. Unfortunately, or fortunately from my POV, I
don't have Cygwin to test with. So any help in getting that code working
is appreciated ;-)



--
-- 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
_______________________________________________
Boost-build mailing list
Boost-build@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-build