Alpha arch development list
 help / color / mirror / Atom feed
From: Bob Tracy <rct@gherkin.frus.com>
To: debian-alpha@lists.debian.org
Cc: linux-alpha@vger.kernel.org
Subject: firefox-esr 52.6.0 available for alpha
Date: Wed, 28 Feb 2018 00:43:54 -0600	[thread overview]
Message-ID: <20180228064354.GA28665@gherkin.frus.com> (raw)

Yes.  Just in case you don't regularly check for updates to the Debian
"unstable/sid" distribution, the long wait for a modern version of
Firefox on the Alpha is over.  For now...

No idea how much longer Michael and I can keep resurrecting Lazarus.
At some point in the near future, it will no longer be possible to build
Firefox on an Alpha unless someone takes up the gauntlet and puts
together a working Rust compiler.  Considering how few of us there are
who might benefit from the effort, it would definitely have to be a
labor of love, performed by someone who does the impossible just because
someone said he couldn't do it.

Of potential interest are some build statistics for Firefox on at least
two different Alpha platforms.  On one of the Debian buildd systems (an
ES45 with 3 CPUs and an unknown amount of RAM), the build took 11:13:17
and approx. 12 GB of disk space.  On my PWS 433au with 1.5 GB of RAM
(maximum amount) and 2.5 GB of swap (pretty much the minimum required),
the build takes over 5 *days* if tests are enabled.

Anyway, enjoy, and pass along your thanks and kudos to Michael.  I'm
pretty much done with Firefox builds on my local machine after this
go-round.  The PWS is too underpowered and otherwise resource-starved
to continue down this road :-(.

--Bob


             reply	other threads:[~2018-02-28  6:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28  6:43 Bob Tracy [this message]
2018-02-28  8:33 ` firefox-esr 52.6.0 available for alpha Michael Cree

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=20180228064354.GA28665@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=debian-alpha@lists.debian.org \
    --cc=linux-alpha@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox