unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Why is IceCat now only 'supported' on Intel-systems?
Date: Thu, 01 Dec 2016 23:58:41 +0100	[thread overview]
Message-ID: <87wpfjmf32.fsf@gnu.org> (raw)
In-Reply-To: <20161201201529.GA29509@macbook42.flashner.co.il> (Efraim Flashner's message of "Thu, 1 Dec 2016 22:15:29 +0200")

Efraim Flashner <efraim@flashner.co.il> skribis:

> On Wed, Nov 30, 2016 at 09:39:40PM -0500, Mark H Weaver wrote:
>> According to:
>> 
>>   https://hydra.gnu.org/eval/109381?filter=icecat#tabs-removed
>> 
>> the jobs for icecat on armhf and mips64el were removed in evaluation
>> 109381 (corresponding to commit 663d5b5), but were present in the
>> previous evaluation 109380 (commit cd65d60).
>> 
>> Can anyone tell me why this happened?
>> 
>> I guess that the 'supported-systems' field of some package that 'icecat'
>> depends on was recently changed, but I was unable to find anything
>> obvious by grepping through the output of "git log -p".
>> 
>> Debian includes Firefox packages for 'armhf' and 'mips64el', so it's
>> obviously possible to get it working on those platforms.
>> 
>> I find it disturbing that we seem to be in the habit of removing
>> non-Intel systems from 'supported-systems' fields in packages that other
>> distros are able to get working on non-Intel.  These are bugs to be
>> fixed, not swept under the rug to get them out of sight.
>> 
>>       Mark
>
> It turns out libjpeg-turbo depends on nasm, which was incorrectly marked
> as only supporting Intel hardware.

Again, there’s no such problem on current master AFAICS:

--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> ,use(guix)
scheme@(guile-user)> ,use(gnu packages assembly)
scheme@(guile-user)> ,use(gnu packages gnuzilla)
scheme@(guile-user)> (package-supported-systems icecat)
$15 = ("x86_64-linux" "i686-linux" "armhf-linux" "mips64el-linux")
scheme@(guile-user)> (package-supported-systems nasm)
$16 = ("x86_64-linux" "i686-linux" "armhf-linux" "mips64el-linux")
scheme@(guile-user)> (package-transitive-supported-systems icecat)
$17 = ("x86_64-linux" "i686-linux" "armhf-linux" "mips64el-linux")
--8<---------------cut here---------------end--------------->8---

and <https://hydra.gnu.org/eval/109381?filter=icecat>.

Am I missing something?

Ludo’.

  reply	other threads:[~2016-12-01 22:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01  2:39 Why is IceCat now only 'supported' on Intel-systems? Mark H Weaver
2016-12-01 14:13 ` Tobias Geerinckx-Rice
2016-12-01 15:29   ` Tobias Geerinckx-Rice
2016-12-01 14:26 ` Ludovic Courtès
2016-12-01 20:15 ` Efraim Flashner
2016-12-01 22:58   ` Ludovic Courtès [this message]
2016-12-02  1:47   ` Mark H Weaver

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=87wpfjmf32.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=efraim@flashner.co.il \
    --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 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).