From: Manolis Ragkousis <manolis837@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Samuel Thibault" <samuel.thibault@gnu.org>
Cc: Guix-devel <Guix-devel@gnu.org>, bug-hurd@gnu.org
Subject: GSoC: Porting Guix to Hurd week 3+4 report.
Date: Sun, 31 May 2015 11:13:44 +0300 [thread overview]
Message-ID: <CAFtzXzOgZ1zLJJunfA7A9iM514JnPjho4j=G4JUnF-0SfLV0+Q@mail.gmail.com> (raw)
Hello Guix, Hello Hurd
Last week I didn't send a report on my progress because I didn't
believe I have anything
of importance to report. So here is a recap of what I did these two
weeks, the problems I
came up with, and the problems I currently have.
1) I sent the patches of the two previews weeks for review, modified
them according to Ludo's
suggestions and most of them are pushed in the right branches.
2) I thought last week I was close in producing the tarballs. I was
wrong. There is a problem
when building %gcc-static that the build fail at libgcc because it
targets the wrong system.
This is what I was investigating the whole week. While trying to find
what's wrong I stumbled
upon these problems:
3) Found a circular dependency between glibc-hurd-headers and
hurd-minimal. Resolved it
and sent a patch to the list. (Ludovic please give it a look :-))
4) tarball-package in make-bootstrap.scm does not give the right name
to the packages it produces.
Changed tarball-package so now we can pass the target to it and as a
result it will use the proper name.
5) gcc-4.7 passes "--with-native-system-header-dir=" which points to
the wrong libc. According to my
understanding this should point to the proper libc to be used in the
target system. Am I right?
6) So the problem with %gcc-static is that libdecnumber: sets "dpd"
while libgcc: sets "no" and we get
a build failure because it can't find "no" in libdecnumber. Found a
similar case here
https://gcc.gnu.org/ml/gcc/2007-03/msg00941.html . Turned everything
in make-bootstrap.scm into procedures
so I am sure it evaluates to the right libc, patched libdecunmber's
and libgcc's configure.ac so they
run AC_CANONICAL_{BUILD,HOST,TARGET} and made sure with the repl that
the right glibc is used.
And still can't find how to solve it. Any suggestions?
I have probably forgot some things but I believe I reported most of
them. I would really like your opinion on
these problems so I can continue.
Manolis
next reply other threads:[~2015-05-31 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 8:13 Manolis Ragkousis [this message]
2015-05-31 20:22 ` GSoC: Porting Guix to Hurd week 3+4 report Ludovic Courtès
2015-06-02 14:06 ` Manolis Ragkousis
2015-06-02 15:55 ` Thomas Schwinge
2015-06-03 21:25 ` Manolis Ragkousis
2015-06-04 20:48 ` Ludovic Courtès
2015-06-07 20:55 ` Thomas Schwinge
2015-06-08 11:43 ` Manolis Ragkousis
2015-06-08 12:59 ` Ludovic Courtès
2015-06-08 13:12 ` 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='CAFtzXzOgZ1zLJJunfA7A9iM514JnPjho4j=G4JUnF-0SfLV0+Q@mail.gmail.com' \
--to=manolis837@gmail.com \
--cc=Guix-devel@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=ludo@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).