Re: Python and debug STLport (was: Re: nocygwin toolset)

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-13 09:36:47

----- Original Message -----
From: "Raoul Gough" <RaoulGough_at_[hidden]>

> From: "David Abrahams" <david.abrahams_at_[hidden]>
>
> > Moving this to jamboost_at_yahoogroups.com...
>
> Yes, sorry about the mis-directed post. I typed the wrong list name by
> mistake.
>
> > From: "Raoul Gough" <RaoulGough_at_[hidden]>
> [snip]
> > > I guess I'll have to put together the changes necessary to build an
> > > NT-native jam using cygwin gcc.
> >
> > I'm sure the jam executable itself is fine, modulo small changes that
may
> > need to be made to the Jambase... hmm, no, there appears to be
something
> > wrong with the way commands are invoked. A Jam built under Cygwin can
> > bootstrap itself, but when used in Boost.Build there is some kind of
> > problem. If you use
> >
> > jam <options> -ofile <targets>
> >
> > It will write a file which you can invoke iwith the shell, FWIW.
>
> I had (probably) the same problem with the cygwin build, but removing the
> assignments of JAMSHELL in tools/build/jam_src/Jambase and
> tools/build/allyourjambase.jam fixed the problem for me. I thought you'd
> already integrated these changes, though, so I'm not sure what's going on
> here.

Yes, AFAIK I did.

> > > There is one remaining problem with python, but it only occurs in the
> > debug
> > > build.

Moving the rest of this response to the Python C++-sig, where it belongs...

-Dave