Re: Latest 64 bit test stuff on sourceware

[Teemu NÃtkinniemi <tnatkinn at gmail dot com>]

On 19.2.2013 20:33, Corinna Vinschen wrote:
> On Feb 19 13:00, Ryan Johnson wrote:
> > 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?
>
> It's not the problem.  This test is always performed by configure and
> it's result is not crucial.  Certain non-gcc compilers apparently know
> a -V flag...

Ok, I tried it again and now it seems to be working. On the other hand, 
Perl compiles nicely but won't run.

(gdb) run --help
Starting program: G:\cygwin64\src\perl-5.16.2\perl.exe --help
[New Thread 5928.0x16e8]
warning: cYgFFFFFFFF 1801E6960 0
[New Thread 5928.0x940]
warning: cYgstd 0x23aa30 d 3

Program received signal SIGSEGV, Segmentation fault.
main (argc=2, argv=0x23aad0, env=0x6000281a0) at perlmain.c:110
110         if (!PL_do_undump) {