all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: can't get past commencement in test-env
Date: Sun, 06 Oct 2019 11:09:50 +0200	[thread overview]
Message-ID: <87mueegrz5.fsf@gnu.org> (raw)
In-Reply-To: <87muenb624.fsf@gmail.com> (Maxim Cournoyer's message of "Sun, 29 Sep 2019 22:11:47 +0900")

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi Caleb!
>>
>> Caleb Ristvedt <caleb.ristvedt@cune.org> skribis:
>>
>>> gcc-boot0 in (gnu packages commencement) compiles subtly differently
>>> when built in a chroot (for example, by an installed daemon) compared to
>>> when built without root privileges (for example, in
>>> test-env). Specifically, the presence of this line in the build log:
>>>
>>> ../../gcc-5.5.0/gcc/genmultilib: ./tmpmultilib: /bin/sh: bad
>>> interpreter: No such file or directory

[...]

> Disregarding the value of chrooted isolated builds, I think Caleb found
> out a valid issue in the Guix (chrooted) build of GCC (the failure to
> find /bin/sh leads to errors in genmultilib producing the library output
> 'lib' rather than '/lib64').
>
> Do you think it's worthy of fixing?

Well, apparently it’s not an issue in practice.  :-)

But yeah, we could investigate what happens in chrooted builds and see
whether genmultilib not finding /bin/sh has consequences we hadn’t seen
so far.

Thanks,
Ludo’.

      reply	other threads:[~2019-10-06  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14  4:21 can't get past commencement in test-env Caleb Ristvedt
2019-09-17 13:52 ` Maxim Cournoyer
2019-09-17 15:04   ` Caleb Ristvedt
2019-09-20  2:52     ` Maxim Cournoyer
2019-09-24  7:36 ` Ludovic Courtès
2019-09-29 13:11   ` Maxim Cournoyer
2019-10-06  9:09     ` 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

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

  git send-email \
    --in-reply-to=87mueegrz5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@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.