From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Caleb Ristvedt <caleb.ristvedt@cune.org>
Cc: guix-devel@gnu.org
Subject: Re: can't get past commencement in test-env
Date: Fri, 20 Sep 2019 11:52:33 +0900 [thread overview]
Message-ID: <87tv977k7i.fsf@gmail.com> (raw)
In-Reply-To: <87ftkvneuq.fsf@cune.org> (Caleb Ristvedt's message of "Tue, 17 Sep 2019 10:04:45 -0500")
Hi Caleb,
Caleb Ristvedt <caleb.ristvedt@cune.org> writes:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hello Caleb,
>>
>> Sorry if this answer is late; I noticed nobody had replied yet, so
>> thought I'd try.
>
> Thanks.
>
>> That's an interesting find! What exactly is the 'test-env'? Do you mean
>> an environment created using 'guix environment --pure' ?
>
> No, test-env is the name of a script generated in the process of
> compiling guix. It's used in running the tests run by 'make check'. The
> main feature is that it runs its own daemon with its own store in a
> subdirectory of the guix source directory named test-tmp/store, so tests
> involving the daemon can be run without needing it already
> installed. Other than that, it works like pre-inst-env for the most
> part.
>
>>> What is The Right Thing™ to do here?
>>
>> Perhaps the best fix would be to find a way to tell gcc to always use
>> "/lib" for its library directory? Perhaps possible via a configure
>> flag? Otherwise by patching the script.
>
> genmultilib takes many arguments, passed to it from the makefile. I'm
> sure there's a combination of values for which it will do what we
> currently do. To work correctly, though, the script will definitely have
> to be patched so that the script it generates has the correct
> interpreter.
>
>> Until we have a need for separating /lib and /lib64 (I guess if we
>> wanted to produce 32 bits variants of packages, that could be useful),
>> we can postpone the big change of using the "correct" library path.
>
> Aye. Changing the builder for gcc-boot0 will cause a full-world rebuild,
> so I suppose it should go in core-updates?
>
> - reepca
core-updates is currently being stabilized (it's in a frozen state).
Perhaps it's best to hold on to publishing this change until
core-updates has been merged to master or else base it on top of the
'core-updates-next' branch, which is used in place of core-updates in
those circumstances.
Maxim
next prev parent reply other threads:[~2019-09-20 2:52 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 [this message]
2019-09-24 7:36 ` Ludovic Courtès
2019-09-29 13:11 ` Maxim Cournoyer
2019-10-06 9:09 ` 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=87tv977k7i.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=caleb.ristvedt@cune.org \
--cc=guix-devel@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.