unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: help-guix@gnu.org, Rene <pacoon@protonmail.com>
Subject: Re: Problem with cross-toolchain support for Hurd
Date: Tue, 28 Aug 2018 11:12:01 +0200	[thread overview]
Message-ID: <87a7p6n9cu.fsf@gnu.org> (raw)
In-Reply-To: <5ed444f6-96d9-5ae1-5e1f-e37e666d056d@gmail.com> (Manolis Ragkousis's message of "Fri, 27 Jul 2018 18:33:31 +0300")

Hi Manolis & Rene!

Manolis Ragkousis <manolis837@gmail.com> skribis:

> On current master I tried running `./pre-inst-env guix build -e '((@@
> (gnu packages cross-base) cross-kernel-headers) "i586-pc-gnu")'` and it
> fails with

Not sure how much of a difference it makes, but I run this command
instead:

--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix build coreutils --target=i586-pc-gnu -K

[...]

checking if i586-pc-gnu-gcc accepts -fno-tree-loop-distribute-patterns with __attribute__ ((__optimize__))... yes
checking for libgd... no
checking for is_selinux_enabled in -lselinux... no
checking for _FORTIFY_SOURCE predefine... no
checking whether i586-pc-gnu-gcc implicitly enables -fstack-protector... no
checking whether the linker provides working __ehdr_start... yes
checking for __builtin_trap with no external dependencies... yes
checking whether the C++ compiler supports thread_local... no
running configure fragment for sysdeps/mach/hurd
checking Hurd header version... bad
configure: error: Hurd headers not installed or too old
Backtrace:
           4 (primitive-load "/gnu/store/vmqv7p9kv7nkpihq708745lghq1…")
In ice-9/eval.scm:
   191:35  3 (_ _)
In srfi/srfi-1.scm:
    640:9  2 (for-each #<procedure 843900 at /gnu/store/f95ghy8mx00…> …)
In /gnu/store/f95ghy8mx00fc22nrvswvnpqlfdkf2nk-module-import/guix/build/gnu-build-system.scm:
   799:31  1 (_ _)
In /gnu/store/f95ghy8mx00fc22nrvswvnpqlfdkf2nk-module-import/guix/build/utils.scm:
    616:6  0 (invoke _ . _)

/gnu/store/f95ghy8mx00fc22nrvswvnpqlfdkf2nk-module-import/guix/build/utils.scm:616:6: In procedure invoke:
Throw to key `srfi-34' with args `(#<condition &invoke-error [program: "/gnu/store/rbrandv7anzjxqkr40d7fkanzssslk4b-bash-minimal-4.4.19/bin/bash" arguments: ("../glibc-2.23-hurd+libpthread-20161218/configure" "CONFIG_SHELL=/gnu/store/rbrandv7anzjxqkr40d7fkanzssslk4b-bash-minimal-4.4.19/bin/bash" "SHELL=/gnu/store/rbrandv7anzjxqkr40d7fkanzssslk4b-bash-minimal-4.4.19/bin/bash" "--prefix=/gnu/store/ba5affambbmg72chssvb13kc18hg4in0-glibc-hurd-headers-cross-i586-pc-gnu-2.23" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" "--enable-add-ons" "--host=i586-pc-gnu" "--enable-obsolete-rpc") exit-status: 1 term-signal: #f stop-signal: #f] a47740>)'.
note: keeping build directory `/tmp/guix-build-glibc-hurd-headers-cross-i586-pc-gnu-2.23.drv-0'
builder for `/gnu/store/fhhyd783ax7n697ngymazqn8y2s1g44d-glibc-hurd-headers-cross-i586-pc-gnu-2.23.drv' failed with exit code 1
@ build-failed /gnu/store/fhhyd783ax7n697ngymazqn8y2s1g44d-glibc-hurd-headers-cross-i586-pc-gnu-2.23.drv - 1 builder for `/gnu/store/fhhyd783ax7n697ngymazqn8y2s1g44d-glibc-hurd-headers-cross-i586-pc-gnu-2.23.drv' failed with exit code 1
cannot build derivation `/gnu/store/nqzms08in49xwsxjwamanx04d58dy6in-hurd-minimal-cross-i586-pc-gnu-0.9.drv': 1 dependencies couldn't be built
cannot build derivation `/gnu/store/1wpn6zk131ca284zqhvifsgm1mv8ap8v-hurd-core-headers-cross-i586-pc-gnu-0.9.drv': 1 dependencies couldn't be built
cannot build derivation `/gnu/store/gncvwffzqcw0khrh53k3q38y6xnbq5qd-perl-5.26.1.drv': 1 dependencies couldn't be built
guix build: error: build failed: build of `/gnu/store/gncvwffzqcw0khrh53k3q38y6xnbq5qd-perl-5.26.1.drv' failed
$ git describe
v0.15.0-1202-ga0a2c2f16
--8<---------------cut here---------------end--------------->8---

… but as you can see the end result is the same.  :-)

I think we can skip this issue though: since ‘core-updates’ has
glibc 2.28, how about merging ‘glibc/linux’ and ‘glibc/hurd’ on
‘core-updates’, removing the Hurd’s ‘libpthread’, and starting from
there?

(Note that the two glibc packages must be merged in a way that does not
involve a full rebuild because ‘core-updates’ is frozen now.)

Thanks,
Ludo’.

      reply	other threads:[~2018-08-28  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27 15:33 Problem with cross-toolchain support for Hurd Manolis Ragkousis
2018-08-28  9:12 ` Ludovic Courtès [this message]

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=87a7p6n9cu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=manolis837@gmail.com \
    --cc=pacoon@protonmail.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.
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).