Re: Latest 64 bit test stuff on sourceware

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

Hi Peter,

On Feb 16 23:17, Peter Rosin wrote:
> On 2013-02-16 13:16, Corinna Vinschen wrote:
> > Here's the list of packages I prepared:
> > 
> >   base-cygwin-toolchain-install-first-20130216.x86_64.tar.xz
> >   coreutils-8.14-1.x86_64.tar.xz
> >   dash-0.5.7-1.x86_64.tar.xz
> >   file-5.11-1.x86_64.tar.xz
> >   findutils-4.5.9-2.x86_64.tar.xz
> >   gawk-4.0.2-1.x86_64.tar.xz
> >   grep-2.6.3-1.x86_64.tar.xz
> >   m4-1.4.16-1.x86_64.tar.xz
> >   make-3.82-1.x86_64.tar.xz
> >   md5.sum
> >   mingw-gdb.x86_64.tar.xz
> >   mintty-r1295.x86_64.tar.xz
> >   rebase-4.4.0-1.x86_64.tar.xz
> >   sed-4.2.1-1.x86_64.tar.xz
> >   tar-1.26-1.x86_64.tar.xz
> >   tcsh-6.18.01-1.x86_64.tar.xz
> > 
> > For installation, start with untar'ing the base-cygwin-* package, which
> > contains cygwin itself and the native toolchain.  Then untar all the
> > other packages on top if it.  In the end, you have dash/sh, and tcsh to
> > work with.  What you need to provide yourself are passwd and group
> > files, as well as fstab and personal profiles to fit your needs.
> 
> Hi!
> 
> I tried this out a little bit. Neat stuff!
> 
> Some comments:
> 
> 1. base-cygwin...tar.xz puts its binaries in /bin, but gcc
> et al expects to be in /usr/bin (I think, at least that was
> the case in the previous version of that tarball). The other
> tarballs but their binaries in /usr/bin. The default mounts:
> [...]
> This issue feels like it's something I've misunderstood.

The base package installs symlinks usr/bin -> ../bin and usr/lib ->
../lib.  This was supposed to solve the problem since when unpacking the
other packages, the 32 bit tar finds the symlinks and installs
everything usr/bin to bin and everything usr/lib to lib, as expected.

Are you saying that didn't work?

> 2. A configure script I ran hit a snag because
> "gcc conftest.c -lc" failed with a missing libc. I know -lc
> isn't needed, but it works with plain old non-64-cygwin. I could
> get past it by seeding the cache, so it's not a show-stopper (at
> least not in this incarnation).

Oh, right.  libc.a, libg.a and libm.a are missing for some reason.
I missed that, sorry.

> 3. The config.status scripts generated by the configure scrips
> I have tested are not working (all Makefiles end up empty), but
> I suspect that's some issue between autoconf and dash. So far it
> has worked to run ./config.status from plain old non-64-cygwin
> between configure and make.

Yes, I noticed this as well.  The blame is either on gawk, or on
the combination of dash and gawk.  For testing I just tried to run
the gawk testsuite (should have done that from the start :-() and
noticed that all output files in the testsuite are generated empty.

Well, bugs were to be expected.  I'll debug that this week (but
obviously have nothing against others debugging this as well...)

Thanks for testing, it's much appreciated.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat