This is the mail archive of the
mailing list for the Cygwin project.
Re: bash broken with cygwin 1.3.20?
- From: Roland Schwingel <Roland dot Schwingel at onevision dot de>
- To: cygwin at cygwin dot com
- Date: Thu, 13 Feb 2003 12:40:19 +0100
- Subject: Re: bash broken with cygwin 1.3.20?
- Organization: OneVision Software AG
- References: <3E4B7F49.email@example.com>
Thanks for your reply...
Well... configure is a shell script. And is executed with bash.
So ok... Bash has the problem in finding the correct file
(configure uses test for this). Of course the failure might be
triggered by a bug in cygwin1.3.20. And maybe it is only a
It appears I made it a bit complicated... Sorry.
But well, the bug (at least on my machines here) persists.
Has anyone else tried this with cygwin 1.3.20?
On Thu, Feb 13, 2003 at 12:19:37PM +0100, Roland Schwingel wrote:
> A few days ago I updated to 1.3.20. Everything was fine till now...
> (All cygwin packages are up to date)
> I tried to recompile gcc (the one from FSF). I am having problems with
> running configure...
> I am on local drive. Imagine /cygdrive/c/temp.
> Image the gcc sources to be in the subfolder gcc-3.2.1
> As suggested by the buildmanual of gcc
> I do
> mkdir gcc-3.2.1_obj
> cd gcc-3.2.1_obj
> ../gcc-3.2.1/configure <whatever options>
> It fails with
> *** "Can't find configure.in. Try using --srcdir=some_dir"
> When trying it with --srcdir=../gcc-3.2.1 it gets a bit further and then
> to be not able to find configuration package of gcc in
> When specifying --srcdir=/cygdrive/c/temp/gcc-3.2.1
> I get the same error with a different location
> When switching back to 1.3.19 (just that module/package nothing else)
> everything is fine again and works as expected (I donot even need to
> use --srcdir)
Sorry but somehow I don't see bash in this figure.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html