Re: [gentoo-alt] FW: x86-winnt

[Fabian Groffen]

On 14-05-2008 09:35:03 +0200, Markus Duft wrote:
> > Today I added the keyword x86-winnt in all places, and also the
> > corresponding profiles. The purpose of this arch is, to get native
> > windows binaries. Native in this case means, that the resulting
> > binaries use the Microsoft windows libc (msvcrt) instead of the interix
> > libc (libc.so). Also those binaries use a different subsystem (console
> > or windows instead of posix), and can run completely without interix
> > installed. The compiler used to create those binaries, does a lot of
> > low-level magic, see [1].

Cool!

> > To keep things separated, those native windows binaries are installed
> > in a "child-prefix". First off all a "parent-prefix" is needed, which
> > is an interix prefix right now (may be cygwin too in the future?). from
> > there the winnt cross compiler is installed (parity). After that I
> > manually created some wrappers right now, but I (and haubi) thought of
> > screwing up the existing gcc-config and binutils-config packages to get
> > those right (FYI I attached the two wrappers). I then symlinked
> > /opt/gentoo.system/usr/i586-pc-winnt6.0/bin/{gcc,ld} to
> > /opt/gentoo.system/usr/bin/i586-pc-winnt6.0-{gcc,g++,ld} (yes, both gcc
> > and g++ point to the gcc wrapper).

I don't think I understand this completely.  Are you doing "normal"
cross-compilation, and/or do you use Portage's ability to use a
different "target" EPREFIX than the configured one?  (e.g. env
EPREFIX="/my/some-arch/prefix" CHOST="some-arch-blaX" emerge mypackage)

> > Now the child-prefix can be set-up with bootstrap-prefix.sh like this:
> >
> > $ CHOST=i586-pc-winnt6.0 EPREFIX=/opt/gentoo.winnt
> > /opt/gentoo.system/usr/portage/scripts/bootstrap-prefix.sh tree
> > $ CHOST=i586-pc-winnt6.0 EPREFIX=/opt/gentoo.winnt
> > /opt/gentoo.system/usr/portage/scripts/bootstrap-prefix.sh setup
> >
> > Now one can emerge winnt packages (only parity so far...):

So what is it?  Is the i?86-pc-winntX a full install (having @system
emerged somehow) or is it only the result of cross-compiled stuff?

> > $ CBUILD=i586-pc-winnt6.0 EPREFIX=/opt/gentoo.winnt emerge -v parity

Hmm... CBUILD?  Isn't the building machine the interix thing?  Correct
me if I'm wrong.  I know haubi did some work on cross-compilation with
Prefix recently, but I haven't managed to catch up with him on that...

> > I must admit, that I didn't use exactly the above steps for
> > bootstrapping the tree, but instead as first step linked my existing
> > /opt/gentoo.system/usr/portage dir to /opt/gentoo.winnt/usr/portage,
> > this saved downloading and unpacking a snapshot (which right now won't
> > work (without updating) anyway, since I just committed the necessary
> > changes :))
> >
> > Phew, that's it for now :) Any questions/comments?

Can we "bootstrap" a winnt system, or do you always keep on needing the
"host" (interix or cygwin in this case).  Is it possible to make say
like an installer that just installs a stage4 Prefix such that you can
start, say bash, from cmd.exe?


-- 
Fabian Groffen
Gentoo on a different level
-- 
gentoo-alt@l.g.o mailing list