From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev@lists.ozlabs.org
Subject: FYI: iceweasel 40.X.X PowerPC isn't available for Debian PPC32
Date: Mon, 7 Sep 2015 13:05:48 +0200 [thread overview]
Message-ID: <55ED6F8C.7050003@xenosoft.de> (raw)
In-Reply-To: <CAK90Sjm5JnDrtVLpUQ2=GJ2zXaX0HGMkdx46ACcHPFP0bxsUmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3193 bytes --]
FYI:
On 07 September 2015 at 11:07 AM, Boris Reinhard
[debian-powerpc@lists.debian.org] wrote:
>
>
> Off-list reply, please don't quote/ forward
>
> Hi,
>
> wrong list, please use this one if you want to reach ppl that do
> active work on ppc:
>
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
> Come to think of it, it might be interesting/ helpful contacting
> Cameron Kaiser (tenfourfox) and Tobias Netzel (webkit for leopard)
> additionally, asking about how or if their ppc osx work could
> potentially/ at all benefit linux ppc!?
>
> Grüße
> Boris Reinhard
>
> Hi All,
>
> Iceweasel was updated to version 40.0.3-3 for the unofficial Debian
> PPC64 port. I installed it inside my Debian PPC64 chroot.
> Unfortunately it doesn't start either.
>
> Note: Iceweasel and Firefox 40.X.X PowerPC aren't available for all
> Ubuntu flavours and for Debian with 32-bit userland currently.
>
> Cheers,
>
> Christian
>
> On 02 September 2015 at 07:38 AM, Christian Zigotzky wrote:
>
> Hi Lennart,
>
> Thank you for your answer.
>
> Unfortunately the increasing of the stack spaces wasn't successfully.
>
> I tried the following stack sizes:
>
> ulimit -s 16384
> ulimit -s 32768
> ulimit -s 65536
> ulimit -s 131072
>
> iceweasel Debian PPC64 in a chroot:
>
> too much recursion
> Segmentation fault
>
> Rgds,
>
> Christian
>
>
> On 01 September 2015 at 8:02 PM, Lennart Sorensen
> [debian-powerpc@lists.debian.org] wrote:
>
> On Tue, Sep 01, 2015 at 07:24:48PM +0200, Christian Zigotzky
> wrote:
>
> Hi All,
>
> Iceweasel and Firefox 40.X.X PowerPC aren't available for
> all Ubuntu
> flavours and for Debian with 32-bit userland currently.
>
> There are build problems:
>
> Iceweasel 40 build status:
> https://packages.debian.org/de/experimental/iceweasel
>
> Firefox 40 build status:
> https://launchpad.net/ubuntu/+source/firefox/
>
> But iceweasel 40.0.3-1 was released for the unofficial
> Debian PPC64 port. I
> installed it inside my Debian PPC64 chroot. Unfortunately
> it doesn't start.
>
> Error messages:
>
> too much recursion
> Segmentation fault
>
> Is anyone working on resolving this issue?
>
> Could you try what happens if you change the stack size limit?
>
> ulimit -s 16384 (I believe the current default that you can
> check with
> ulimit -a is 8192). Could even try something even bigger like
> 65536.
> Then run firefox from that terminal where you changed the limit
> temporarily.
>
> Certainly with 64 bit pointers and 64 bit registers, ppc64
> could be using
> quite a bit of stack space in the javascript engine, which
> appears to
> be the thing that always causes this error in firefox (seems
> to happen
> everytime they change the engine in a major way, and then
> things get
> tweaked until it works again, then it gets broken again).
>
>
>
[-- Attachment #2: Type: text/html, Size: 5622 bytes --]
parent reply other threads:[~2015-09-07 11:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAK90Sjm5JnDrtVLpUQ2=GJ2zXaX0HGMkdx46ACcHPFP0bxsUmA@mail.gmail.com>]
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=55ED6F8C.7050003@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).