Latest 64 bit test stuff on sourceware

Ryan Johnson ryan.johnson@cs.utoronto.ca
Tue Feb 19 18:27:00 GMT 2013


On 19/02/2013 12:14 PM, Teemu Nätkinniemi wrote:
> On 19.2.2013 19:09, Corinna Vinschen wrote:
>> On Feb 19 19:01, Teemu Nätkinniemi wrote:
>>> On 19.2.2013 18:41, Corinna Vinschen wrote:
>>>> On Feb 19 15:48, Corinna Vinschen wrote:
>>>>> On Feb 19 06:14, Yaakov wrote:
>>>>>> On Tue, 19 Feb 2013 10:24:52 +0100, Corinna Vinschen wrote:
>>>>>>> I just uploaded
>>>>>>> ftp://cygwin.com/pub/cygwin/64bit/install/base-cygwin-toolchain-install-first-20130219.x86_64.tar.xz 
>>>>>>>
>>>>
>>>> Replaced with
>>>> ftp://cygwin.com/pub/cygwin/64bit/install/base-cygwin-toolchain-install-first-20130219-2.x86_64.tar.xz 
>>>>
>>>
>>> This last update seems to have broken GCC.
>>
>> How so?  It seems to work for me with a simple example. Ideally, bug
>> reports come with details...
>
> Sorry, I was in the middle of trying to get Perl working so I replaced 
> it with the previous version. Here's an excerpt from a not very 
> informative config.log.
>
> configure:2922: $? = 0
> configure:2929: gcc -v >&5
> Using built-in specs.
> COLLECT_GCC=gcc
> Target: x86_64-pc-cygwin
> Configured with: /home/corinna/src/cross-cygwin/gcc/configure 
> --host=x86_64-pc-cygwin --target=x86_64-pc-cygwin --prefix=/usr 
> --sysconfdir=/etc --enable-languages=c,c++ --disable-shared 
> --enable-static
> Thread model: single
> gcc version 4.8.0 20130215 (experimental) (GCC)
> configure:2933: $? = 0
> configure:2940: gcc -V >&5
> gcc: error: unrecognized command line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
That's odd... I don't think -V has ever been a legal command-line option 
to gcc. Was that supposed to be -v?

Ryan



More information about the Cygwin-developers mailing list