unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] build: Correctly determine the system type for GNU/Hurd systems.
Date: Sun, 26 Jun 2016 23:34:02 +0200	[thread overview]
Message-ID: <87bn2nk52t.fsf@gnu.org> (raw)
In-Reply-To: <e45c0790-79d0-2629-56d1-d4f4aa853808@gmail.com> (Manolis Ragkousis's message of "Thu, 23 Jun 2016 19:17:06 +0300")

Hi!

Manolis Ragkousis <manolis837@gmail.com> skribis:

> On 06/19/16 16:57, Ludovic Courtès wrote:
>> I wonder why this is needed though; normally, when building on
>> i586-unknown-gnu*, the next case:
>> 
>> --8<---------------cut here---------------start------------->8---
>>      case "$host_os" in
>>        linux-gnu*)
>> 	  # For backward compatibility, strip the `-gnu' part.
>> 	  guix_system="$machine_name-linux";;
>>        *)    # ← THIS CASE
>> 	  # Strip the version number from names such as `gnu0.3',
>> 	  # `darwin10.2.0', etc.
>> 	  guix_system="$machine_name-`echo $host_os | "$SED" -e's/[0-9.]*$//g'`";;
>>      esac
>> --8<---------------cut here---------------end--------------->8---
>> 
>> … should produce “i586-gnu”, no?  What did you observe?  To put it
>> differently, what does ./build-aux/config.guess return on a GNU/Hurd
>> system?
>
> It produces "i686-gnu0.8" which is problematic and we expect "i586-gnu"
> for our binaries to work.

OK.  I can imagine that config.guess cannot distinguish between i686 and
i586; the “0.8” part is fun and much less expected (the last GNU release
that ever happened was called “0.3” :-)).

> I will push the updated patch to core-updates.

Perfect, thanks!

Ludo’.

      reply	other threads:[~2016-06-26 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17 19:04 [PATCH] build: Correctly determine the system type for GNU/Hurd systems Manolis Ragkousis
2016-06-19 13:57 ` Ludovic Courtès
2016-06-23 16:17   ` Manolis Ragkousis
2016-06-26 21:34     ` 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=87bn2nk52t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=manolis837@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 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).