unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Manolis Ragkousis <manolis837@gmail.com>
To: Guix-devel <Guix-devel@gnu.org>, bug-hurd@gnu.org
Cc: Samuel Thibault <samuel.thibault@gnu.org>
Subject: GSoC: Porting Guix to Hurd week 1 report
Date: Thu, 7 May 2015 22:12:32 +0300	[thread overview]
Message-ID: <CAFtzXzPDMbUiL4PkR8PPdf8CU-WuUGMYsTeZ50b8=UwsJvZ=XQ@mail.gmail.com> (raw)

Hello Guix, Hello Hurd

I think it's time for my first report so everyone is up to date .
I will describe what happened in chronological order:

1) Pushed acl patch to wip-hurd so coreutils can be built for
target=i686-pc-gnu.
2) Simplified our glibc-hurd and hurd minimal package, thanks to
the latest release of gnumach, mig and hurd.
3) Started building one by one the binaries need for the bootstrap-
binaries.
4) Modified our package definitions for sed, patch and tar so PATH_MAX
will be passed to configure.
5) When trying to patch tar I discovered that anything before the
patch package definition could not be built. Source patching in
‘patch-and-repack’ would use not the tar from ‘%final-inputs’,
but the tar built with ‘%final-inputs’. Ludovic fixed it.
6) The problem with tar was that D_INO_IN_DIRENT is not present in hurd. It is
fixed in upstream tar repo in e9ddc08da0982f36581ae5a8c7763453ff41cfe8. Just
aplied that patch.
7) All the binaries needed for bootstrapping can be built with our i686-pc-gnu
toolchain.
8) Starting working on getting the bootstrap-tarballs built.
9) Added a glibc-for-target macro so make-bootstrap.scm will choose
the right glibc
depending on target.

I think that's it for now. If you have any questions please feel free to ask :-)

Manolis

             reply	other threads:[~2015-05-07 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 19:12 Manolis Ragkousis [this message]
2015-05-08 14:44 ` GSoC: Porting Guix to Hurd week 1 report Ludovic Courtès
2015-05-09 10:53   ` Manolis Ragkousis

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFtzXzPDMbUiL4PkR8PPdf8CU-WuUGMYsTeZ50b8=UwsJvZ=XQ@mail.gmail.com' \
    --to=manolis837@gmail.com \
    --cc=Guix-devel@gnu.org \
    --cc=bug-hurd@gnu.org \
    --cc=samuel.thibault@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).