cygwin configure problem

[Smith, Gene]

Ralf Corsepius wrote, On 8/18/2004 1:10 AM:

> On Wed, 2004-08-18 at 05:34, Gene Smith wrote:
> 
>>Ralf Corsepius wrote, On 08/17/2004 09:44 PM:
>>
>>>On Tue, 2004-08-17 at 19:23, Smith, Gene wrote:
>>>
>>>
>>>>Ralf Corsepius wrote, On 8/17/2004 11:47 AM:
>>>>
>>>>
>>>>
>>>>>On Tue, 2004-08-17 at 17:16, Smith, Gene wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>cd `pwd`
>>>>>>Pwd generates a string containing "Documents and Settings" but cd 
>>>>>>trucates it at the first un-escaped space producing just ".../Documents" 
>>>>>>which causes the choke.
>>>>>>
>>>>>>Guess I will have to move my rtems stuff to where the cygwin path 
>>>>>>contains no spaces.
>>>>>
>>>>>Exactly. It's a general limitation with all autoconf generated configure
>>>>>scripts. There are occasions where quoting strings containing white
>>>>>spaces fail. Sometimes, the cause is a bug in autoconf, sometimes the
>>>>>cause is a bug in the shell being used, sometimes it's a bug elsewhere.
>>>
>>>FWIW: The bug you've hit is a quoting bug in RTEMS. 
>>>
>>>Once having fixed this one you'll trip a similar known quoting bug in
>>>autoconf, which already had been fixed in autoconf CVS, but is still
>>>open in released version. Later, you'll trip yet another a new quoting
>>>bug in autoconf :)
>>
>>Any bugzilla numbers for these looming bugs?
> 
> 
> I believe to have fixed the RTEMS specific bugs in rtems-4.7/CVS-head
> and submitted a fix to one of the autoconf bugs to the
> autoconf-patches at gnu.org, a couple of hours ago.
> 
> A fix to other autoconf bug is in autoconf-CVS and is dated 2003-11-24.
> 
> I have prepared a patch to autoconf-2.59 comprising both
> autoconf-patches and have placed it into RTEMS-CVS.
> http://www.rtems.org/cgi-bin/gnatsweb.pl?database=RTEMS&cmd=view&pr=672
> 
> I am not sure, if this issue is serious enough to justify backporting
> the bug-fixes to rtems-4.6.
> 
> 
>>>>>Rule of thumb: Don't use whitespaces.
>>>>>
>>>>>Ralf
>>>>
>>>>I agree. They are evil in pathnames, email address, URLs etc. But some
>>>>OS vendors seem to encourage them. ;)
>>>>
>>>>Anyhow, I moved my rtems stuff to a space-free path and now am stumped
>>>>again. Spits out this after going a while,
>>>>
>>>>configure: error: invalid variable name: build_alias
>>>>configure: error: /bin/sh
>>>>'../../../../rtems-4.6.1/tools/cpu/generic/configure' failed for generic
>>>>configure: error: /bin/sh '../../../rtems-4.6.1/tools/cpu/configure'
>>>>failed for tools/cpu
>>>
>>>This issue had been reported many times (Please check this list's
>>>archives). 
>>>
>>>I am not using Cygwin myself, and therefore hardly can help, but AFAIU
>>>the Cygwin users' reports, this is a bug in Cygwin.
>>>
>>>Ralf
>>
>>Yes, I could see it was reported but a definite reason was never given. 
>>(Sometimes shutting down virus checking and other programs helped.) Has 
>>anyone actually used cygwin to build and manage a successful rtems project?
> 
> <wild guesses>
> I'd guess it to be an address violation deep inside of Cygwin or Win,
> probably being triggered by a memory leak or buffer overrun somewhere.
> So I'd assume the "virus protection stuff interferences" actually to be
> secondary effects.
> 
> Some users had reported only particular Cygwin and Win versions to be
> affected, so I would not exclude upgrading Cygwin could help.

I am not an expert on cygwin but I think I have the latest version since 
  I user the cyg-setup.exe method which connects you online and keeps 
you up to date when you upgrade or install a new package.

> 
> Other users reported switching the shell being used as /bin/sh helped
> [Some versions of Cygwin use a broken "ash" as /bin/sh. Using bash or
> ksh as /bin/sh (copying bash/ksh to /bin/sh) sometimes has helped.
> zsh, pdksh and dash are known to suffer from general bugs, but if all
> else fail, they also are worth a try.]

I upgraded my cygwin bash to the latest and made sure /bin/sh was in 
fact the same as /usr/bin/bash which is bash.

> 
> Another potential issue with Cygwin is environment variables interfering
> (LIBS, OBJS, CFLAGS, CPPFLAGS etc.). There are spots inside of the
> Makefiles where they can interfere, but I don't see how this can take
> effects, here.

This sounds like something to look into. I couldn't get rtems to build 
on linux either. The problem was that I needed the <INSTALL_PT>/bin 
first in the path rather than last as show on pg 27 of "Getting Started..."

Thanks for the guesses and details on the "looming" bugs
-gene

> </wild guesses>
> 
> Ralf
> 
>