Re: cause for armel nss (i.e., firefox) build segfault

Wookey wrote: On 2007-05-06 03:40 +0200, Lennert Buytenhek wrote: Hi, The reason that building nss (i.e., firefox) would segfault on ARM EABI systems is an assumption about the layout of the jmp_buf structure in the nspr library (which nss depends on) that does hold on old-ABI but no longer

Re: cause for armel nss (i.e., firefox) build segfault

On 2007-05-06 03:40 +0200, Lennert Buytenhek wrote: > Hi, > > The reason that building nss (i.e., firefox) would segfault on ARM EABI > systems is an assumption about the layout of the jmp_buf structure in > the nspr library (which nss depends on) that does hold on old-ABI but > no longer holds on

cause for armel nss (i.e., firefox) build segfault

Hi, The reason that building nss (i.e., firefox) would segfault on ARM EABI systems is an assumption about the layout of the jmp_buf structure in the nspr library (which nss depends on) that does hold on old-ABI but no longer holds on EABI. The attached patch fixes this assumption, and fixes the

Re: Endianess question

Wolf-Rüdiger Jürgens wrote: > I see that the Debian NSLU2 is little-endian but many other Arm boards > using Big-endian. (Arcom, Snapgear ...). > What is the reason for using Little/Big Endian? It usually simply depends on which endianness the reference software development kit for that particular

Re: Endianess question

On 2007-05-05 09:46 +0200, Wolf-Rüdiger Jürgens wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I see that the Debian NSLU2 is little-endian but many other Arm boards > using Big-endian. (Arcom, Snapgear ...). It's more complicated than that. Some CPUs/boards can run big or little en

Endianess question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I see that the Debian NSLU2 is little-endian but many other Arm boards using Big-endian. (Arcom, Snapgear ...). What is the reason for using Little/Big Endian? TYA Wolf -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using Gnu