From: Manolis Ragkousis <manolis837@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: cross-libc: Cross build the correct libc for GNU/Hurd systems.
Date: Thu, 16 Jun 2016 21:44:12 +0300 [thread overview]
Message-ID: <616bc2ee-1d2c-d39c-5cfb-5a602439497b@gmail.com> (raw)
In-Reply-To: <6bf591cf-2ea4-01fc-bd13-23ae60864714@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
Hello again,
On 06/16/16 19:32, Manolis Ragkousis wrote:
>> Other than that it LGTM, but if, and only if, you can verify that this
>> does not cause any regression for other cross-compilation targets.
>> Normally this should not change derivations at all so you don’t even
>> need to build them. Just run this:
>>
>> ./pre-inst-env guix build gcc --target=mips64el-linux-gnu -d
>>
>> both before and after the change, and the result should be the same .drv
>> file name.
>
> The derivations are not the same so I will have to build it and see if
> it works. I will report back on that.
>
Cross building gcc 6.1.0 for mips fails with or without my patch on the
latest core-updates.
Other packages build without an issue.
Manolis
[-- Attachment #2: yfy4zqizrsr9kx016mraira0irmxf5-gcc-6.1.0.drv.bz2 --]
[-- Type: application/x-bzip, Size: 441625 bytes --]
next prev parent reply other threads:[~2016-06-16 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 14:43 [PATCH] gnu: cross-libc: Cross build the correct libc for GNU/Hurd systems Manolis Ragkousis
2016-06-12 11:48 ` Manolis Ragkousis
2016-06-12 16:38 ` Ludovic Courtès
2016-06-16 16:32 ` Manolis Ragkousis
2016-06-16 18:44 ` Manolis Ragkousis [this message]
2016-06-26 21:31 ` Ludovic Courtès
2016-07-19 16:30 ` Manolis Ragkousis
2016-07-20 7:16 ` Vincent Legoll
2016-07-20 11:39 ` Manolis Ragkousis
2016-07-22 12:55 ` 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
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=616bc2ee-1d2c-d39c-5cfb-5a602439497b@gmail.com \
--to=manolis837@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).