Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2018-05-11 Thread Mike Hommey
On Fri, May 11, 2018 at 08:49:41PM +0200, John Paul Adrian Glaubitz wrote: > Hi! > > With Firefox 60.0 ESR now in experimental, most of the sparc64-related patches > are now part of the upstream source. > > The only patches we actually need are the one to fix skia on big-endian > targets > (I

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2018-05-11 Thread John Paul Adrian Glaubitz
On 05/11/2018 11:20 PM, Mike Hommey wrote: >> The only patches we actually need are the one to fix skia on big-endian >> targets >> (I am currently in the process of upstreaming this one) and one tiny patch >> to fix an alignment issue on sparc64. > > For the record, the latter was explicitly

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2018-05-11 Thread John Paul Adrian Glaubitz
Hi! With Firefox 60.0 ESR now in experimental, most of the sparc64-related patches are now part of the upstream source. The only patches we actually need are the one to fix skia on big-endian targets (I am currently in the process of upstreaming this one) and one tiny patch to fix an alignment

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2017-06-18 Thread John Paul Adrian Glaubitz
Control: reassign -1 firefox-esr Hello! Since the latest firefox package requires rustc now which isn't available on sparc64 yet, I have ported the sparc64 support patch to the firefox-esr package. I am attaching the updated patch. Could it be applied for the next upload, please? The patch is

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-12-30 Thread John Paul Adrian Glaubitz
Control: retitle -1 firefox: Fix broken sparc64 build support Attaching an updated patch and retitled the bug report since this isn't just platform definitions which are wrong but some more issues have to be addressed. Would be great to have this patch with the sparc64 as well as the m68k build

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-12-12 Thread John Paul Adrian Glaubitz
Control: tags + patch The attached patch fixes Firefox on sparc64 for me. The compiled binary runs but crashes at some point with SIGBUS. This should be easy to debug with gdb though. Will give a try later. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer -

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-12-12 Thread John Paul Adrian Glaubitz
On 12/12/2016 12:38 AM, John Paul Adrian Glaubitz wrote: > On 12/12/2016 12:20 AM, John Paul Adrian Glaubitz wrote: >> Attaching my latest patch which makes use of the ARM64 memory allocator, >> both for the >> Javascript engine as well as mozjemalloc. It seems to fix the memory >> corruption

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-12-11 Thread John Paul Adrian Glaubitz
On 12/12/2016 12:20 AM, John Paul Adrian Glaubitz wrote: > Attaching my latest patch which makes use of the ARM64 memory allocator, both > for the > Javascript engine as well as mozjemalloc. It seems to fix the memory > corruption and > allocation issues, but Firefox now crashes with SIGBUS in

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-12-11 Thread John Paul Adrian Glaubitz
Attaching my latest patch which makes use of the ARM64 memory allocator, both for the Javascript engine as well as mozjemalloc. It seems to fix the memory corruption and allocation issues, but Firefox now crashes with SIGBUS in the xulrunner stub (see below). If anyone wants to have a go at

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-05-22 Thread John Paul Adrian Glaubitz
On 05/22/2016 11:49 AM, John Paul Adrian Glaubitz wrote: > I have been playing a bit more and tried a dirty hack to convince mmap to not > ignore the hint, I just substracted random(), e.g.: > > ret = mmap(addr-random(), size, PROT_READ | PROT_WRITE, MAP_PRIVATE | > MAP_ANON, -1, 0); > > in

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-05-22 Thread John Paul Adrian Glaubitz
I have been playing a bit more and tried a dirty hack to convince mmap to not ignore the hint, I just substracted random(), e.g.: ret = mmap(addr-random(), size, PROT_READ | PROT_WRITE, MAP_PRIVATE | MAP_ANON, -1, 0); in memory/mozjemalloc/jemalloc.c in pages_map(). This actually fixes the

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-05-20 Thread John Paul Adrian Glaubitz
On Fri, May 20, 2016 at 11:06:06PM +0200, John Paul Adrian Glaubitz wrote: > Thus, in order to fix this issue on sparc64/Linux, a more elaborate > fix will have to be developed. I just made a test installation of NetBSD to verify the theory. On Linux: glaubitz@ikarus:~$ cat vmtest.c #include

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-05-20 Thread John Paul Adrian Glaubitz
Hi! Some more updates: Jose Marchesi from Oracle has provided me with two old patches that were used to address the problem with Firefox 17. Those patches are: - xulrunner-linux-sparc64-xpcom.patch - xulrunner-linux-sparc64.patch Those patches didn't apply anymore right away. I had to update

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-05-20 Thread John Paul Adrian Glaubitz
On 05/16/2016 10:15 AM, John Paul Adrian Glaubitz wrote: > After applying both patches, the build *almost* finishes on sparc64, > in fact, it fails at dh_auto_install with [2]: > > Executing /<>/build-browser/dist/bin/xpcshell -g > /<>/build-browser/dist/bin/ -a > /<>/build-browser/dist/bin/ -f

Bug#824449: firefox: FTBFS on sparc64 due to wrong platform definitions

2016-05-16 Thread John Paul Adrian Glaubitz
Source: firefox Version: 46.0.1-1 Severity: normal Tags: patch User: debian-sp...@lists.debian.org Usertags: sparc64 Hi! I have had a look at the firefox package on sparc64 and I was able to detect two problems with platform definitions which prevent an almost successful build on this