From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: cross-base: Add libc/hurd.
Date: Sat, 06 Dec 2014 23:21:34 +0100 [thread overview]
Message-ID: <87fvcsv2q9.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzNFrenC=C1o_sLoN9MEMX3iyK4v8Ayeie57NQon8ZFGgQ@mail.gmail.com> (Manolis Ragkousis's message of "Mon, 1 Dec 2014 22:43:45 +0000")
Manolis Ragkousis <manolis837@gmail.com> skribis:
> For the next step, I must do the appropriate changes to cross-gcc in
> crossbase.scm so I can build it using the new glibc and the hurd
> headers instead of the linux ones. There are also some changes to be
> done in bootstrap.scm (like adding the dynamic linker for i686-gnu).
>
> I expect many changes to the whole guix bootstrapping building
> process, but one thing at a time. WDYT?
I think these will be primarily changes to cross-base.scm, so we can
cross-build the final GCC against the final cross-built libc. The
‘dynamic-linker’ procedure will also need to be adjusted, indeed.
I’m not sure what else might be missing for the cross-GCC. We’ll see? :-)
We’ll need to merge wip-hurd at some point. We’ll have to make sure the
existing cross tool chains are not broken. Could you make sure with:
./pre-inst-env guix build coreutils --target=mips64el-linux-gnu
Alternately, we could set up Hydra to build the branch.
HTH,
Ludo’.
next prev parent reply other threads:[~2014-12-06 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 10:27 [PATCH] gnu: cross-base: Add libc/hurd Manolis Ragkousis
2014-10-29 23:04 ` Ludovic Courtès
2014-11-01 9:44 ` Manolis Ragkousis
2014-11-09 10:41 ` Manolis Ragkousis
2014-11-19 10:26 ` Ludovic Courtès
2014-11-30 19:01 ` Manolis Ragkousis
2014-11-30 22:31 ` Ludovic Courtès
2014-12-01 22:43 ` Manolis Ragkousis
2014-12-06 22:21 ` Ludovic Courtès [this message]
2014-12-06 22:53 ` Manolis Ragkousis
2014-12-07 20:27 ` Ludovic Courtès
2014-11-19 10:20 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvcsv2q9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=Guix-devel@gnu.org \
--cc=manolis837@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.