Hello! While looking at the FTBFS of Firefox, I noticed that Firefox, more precisely ipc/chromium was checking for the definition of __sparc64__ to configure the code for sparc64 [1]. However, when looking at the actual gcc configuration dump, it's apparent that __sparc64__ is actually not used but __arch64__: root@landau:~# echo | gcc -E -dM - |grep __arch64__ #define __arch64__ 1 root@landau:~# echo | gcc -E -dM - |grep __sparc64__ root@landau:~# Changing the header in Firefox's code base actually fixed this particular issue with the firefox package on Debian. Thus, my suspicion is that there might be other packages which are incorrectly configured on sparc64 and consequently either failing to build from source, crashing their testsuite or crashing during operation. A list of the possibly affected packages can be found in [2]. Any comments? Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824449 > [2] https://codesearch.debian.net/results/__sparc64__/page_0 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@xxxxxxxxxx `. `' Freie Universitaet Berlin - glaubitz@xxxxxxxxxxxxxxxxxxx `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
