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 2 report
Date: Fri, 15 May 2015 22:17:14 +0300 [thread overview]
Message-ID: <CAFtzXzPsAQpenXKLP2t0zQ_cM9MRJrDkTSw9+2a5JMNyi9KUYQ@mail.gmail.com> (raw)
Hello Guix, Hello Hurd
Time for the second report. Will report what happened in chronological
order like the last time.
1) I modified gnumach-headers and hurd-headers packages so they will use
"--build=i686-pc-gnu" only when not cross-building.
2) Mig needs flex for both build and run time. So I added flex as both an input
and a native input. Before we were getting a linking error when cross-building.
3) Flex and bison could not be built with when targeting the hurd.
This was because of the
dependency lists m4->bison-2.7->flex and m4->bison.
4) m4 for some reason would run make test even when cross-compiling.
So when hurd
was targeted (and mips as Ludovic pointed out today) it would fail. I
disabled the tests
when cross-building in my local repo and spent quite some time waiting
for the whole
rebuild to finish :P. In any case, Ludovic pushed today at master, a
patch that fixes that.
5) Tomorrow if not today I will have ready the bootstrap-tarballs. I
modified make-boostrap.scm
to use the hurd headers, and everything up to %glibc-bootstrap-tarball
builds fine. I am waiting
for the current build to finish to report on the rest.
There was a problem with the libpthread native input where
(copy-recursively (assoc-ref inputs
"libpthread") "libpthread") would evaluate to (copy-recursively #f
"libpthread"), when creating the tarballs.
I changed it to use %build-inputs and it seemed to work, but after
Thomas uploaded the
glibc-hurd+ libpthread tarball, I removed the problematic part all together.
In any case we should still investigate this one.
6) As I said above Thomas uploaded today a glibc-hurd+ libpthread
tarball. With this, our package
definition for glibc/hurd became as simple as it could possibly get in
this form. The patches are gone.
I can sleep with ease now. Thank you Thomas :-).
I was thinking about following Mark's suggestion of having a generic
glibc package with all the common
configure flags and inputs, and the two others inheriting from it,
defining the specific sources and
inputs/flags. WDYT?
Ludovic I don't have anything to report on the binaries actually
running on hurd right now,
because I am hoping to test that with the actual bootstrap tarballs.
I think that's it for this week. If you have any questions please feel
free to ask :-)
Manolis
next reply other threads:[~2015-05-15 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 19:17 Manolis Ragkousis [this message]
2015-05-16 7:06 ` GSoC: Porting Guix to Hurd week 2 report Andreas Enge
2015-05-16 19:11 ` 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=CAFtzXzPsAQpenXKLP2t0zQ_cM9MRJrDkTSw9+2a5JMNyi9KUYQ@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 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.