From: Tobias Geerinckx-Rice <me@tobias.gr>
To: mhw@netris.org, guix-devel@gnu.org
Subject: Re: Why is IceCat now only 'supported' on Intel-systems?
Date: Thu, 1 Dec 2016 15:13:32 +0100 [thread overview]
Message-ID: <1047188c-73f6-58c8-b84f-e801ff049940@tobias.gr> (raw)
In-Reply-To: <87y400fk43.fsf@netris.org>
[-- Attachment #1.1: Type: text/plain, Size: 1235 bytes --]
Mark
On 01/12/16 03:39, 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?
Most very likely my 7cba764 commit, ‘icecat: Use libjpeg-turbo instead
of bundled libjpeg’[-turbo].
The ‘libjpeg-turbo’ package depends on ‘nasm’, which I didn't realise
was only supported on x86.
> Debian includes Firefox packages for 'armhf' and 'mips64el', so it's
> obviously possible to get it working on those platforms.
I'll take a look. IceCat's bundled ‘libjpeg’ is really the (a?) -turbo
variant, so it shouldn't matter, but I obviously missed something.
> 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.
While a valid sentiment, that's not what happened here.
Kind regards,
T G-R
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 476 bytes --]
next prev parent reply other threads:[~2016-12-01 14:14 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1047188c-73f6-58c8-b84f-e801ff049940@tobias.gr \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.