Re: [RFT PATCH v4 0/8] Sysroot series

[Charles Wilson]

On 8/1/2010 2:43 PM, Ralf Wildenhues wrote:
> I can't really give a good review of the rest without a sysrooted
> compiler, and I don't have time to build one any more this weekend,
> so I'd appreciate if you could post output of
>   make check-local TESTSUITEFLAGS='-v -d -x -k sysroot'
>
> for both w32 and GNU/Linux (and other systems you happen to be able to
> test); thanks.  Might still take me until next weekend though, sorry.

I can do:

  cygwin->mingw  (compiler is sysrooted, and the contents of the
                 sysroot were all compiled with --prefix=/mingw, not
                 --prefix=/the-sysroot/mingw)

  linux->mingw   (compiler is sysrooted, but the contents of the
                 sysroot were all compiled with
                 --prefix=/the-sysroot/mingw [*])

but it will have to wait until the current cygwin testsuite run finishes
(in about four more hours).

[*] This really won't have an effect on libtool's own internal tests.
Its effects will only become visible once you start trying to link
chains of libraries with dependencies, where some (say, the
distribution-provided ones) use --prefix=/the-sysroot/mingw, but your
custom compiled ones, built using the spiffy new libtool --with-sysroot
support, use --prefix=/mingw + DESTDIR=/the-sysroot.

I'll probably deploy a test release of libtool-for-cygwin as soon as
Paolo's v5 (with nit-fixes) is pushed to that temp branch.  The
maintainer of cygwin's package builder tool (cygport) is very anxious to
publish an updated version of that builder tool with support for cross
toolchains, and the design decisions he makes in that process depend on
how much support/how good the support for such things are within
libtool. (Specifically, he's trying to decide between --prefix=/mingw
and --prefix=/$sysroot/mingw.  Libtool is not the only issue; there are
also problems with foo-config scripts, and pkg-config .pc files...)  So
I want to give him some preliminary stuff to test and evaluate.

> Also, I still don't quite understand why this is unusable when the
> compiler is not sysrooted, so an explanation would be nice.  For
> example, the w32 cross compiler package on Debian is not sysrooted.

That does seem to be the case (geez, why did http://packages.debian.org/
switch to only making the patches and stuff available via bzr and not
via the a web interface?).

Obviously, libtool can't autodetect the sysroot if `gcc -print-sysroot`
returns empty (or an error).  So, the only hope here would be to use
--with-sysroot=/explicit/path; I'm not sure what explicit/path you would
use tho.  There don't seem to be any "debian" packages compiled USING
their cross compiler (e.g. analogous to the Fedora-mingw project's
collection http://www.annexia.org/fedora_mingw like "mingw-freetype" or
"mingw-gtk2" so there's no guidance there.

It seems debian's mingw32-runtime package
  http://packages.debian.org/sid/all/mingw32-runtime/filelist
compiles and installs as if --prefix=/usr/i586-mingw32msvc, so maybe you
could try "--sysroot=/usr/i586-mingw32msvc" with --prefix=/.

To test this, I'd need to set up a virtualbox with debian...that might
take a while, so no promises.

--
Chuck