Steve,
On Tue, Feb 21, 2006 at 09:31:48AM -0500, Stephen Gross wrote:
> >Just to be sure, what does the following indicate?
> $ cygcheck -c cygwin
> Cygwin Package Information
> Package VersionStatus
> cygwin 1.5.18-1 OK
Try reinstalling Cygwin 1.5.18
>Just to be sure, what does the following indicate?
$ cygcheck -c cygwin
Cygwin Package Information
Package VersionStatus
cygwin 1.5.18-1 OK
>BTW, can you use the pre-built Python 2.4.1 that is part of the standard
Cygwin distribution?
Nope--I need to
Steve,
On Mon, Feb 20, 2006 at 11:49:06PM -0500, Stephen Gross wrote:
> >On Mon, Feb 20, 2006 at 12:24:34PM -0800, mrstephengross wrote:
> >>Ok, I'm working on building python 2.4.2 on cygwin. I *think* it's
> >>version 3.0 or 3.1 (is there a quick way to find
> On Mon, Feb 20, 2006 at 12:24:34PM -0800, mrstephengross wrote:
>> Ok, I'm working on building python 2.4.2 on cygwin. I *think* it's
>> version 3.0 or 3.1 (is there a quick way to find out what version of
>> cygwin is running within a shell?)
>
> Use &quo
Steve,
On Mon, Feb 20, 2006 at 12:24:34PM -0800, mrstephengross wrote:
> Ok, I'm working on building python 2.4.2 on cygwin. I *think* it's
> version 3.0 or 3.1 (is there a quick way to find out what version of
> cygwin is running within a shell?)
Use "uname -r".
Ok, I'm working on building python 2.4.2 on cygwin. I *think* it's
version 3.0 or 3.1 (is there a quick way to find out what version of
cygwin is running within a shell?)
Anyway, it appears to 'configure' fine, but gcc reports a compile error
when it gets to posixmodule.c.
