Re: Bus error while building Erlang
On 11/25/07, Josip Rodin [EMAIL PROTECTED] wrote: On Sat, Nov 24, 2007 at 01:34:04PM +0300, Sergei Golovan wrote: Hi! Recent build of erlang package failed on sparc architecture (http://buildd.debian.org/build.php?pkg=erlangarch=sparcfile=log). I cannot find a reason looking at the log file, and I don't have an access to any sparc machine to debug the failure. Could someone help me with an access to one of Debian sparc machines? I tried to install Debian in QEMU but it emulates an old hardware which is unsupported by sid. You can log into sperger.debian.org, a recently set up developer-access sparc machine, and try the build there. Unfortunately, I cannot reproduce the bug on sperger. Erlang builds fine. So, it looks like the bug is indeed in gcc or kernel or glibs or whatever (not in erlang). The questions are now how to debug it and where to ask for help with it. -- Sergei Golovan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bus error while building Erlang
Unfortunately, I cannot reproduce the bug on sperger. Erlang builds fine. So, it looks like the bug is indeed in gcc or kernel or glibs or whatever (not in erlang). The questions are now how to debug it and where to ask for help with it. I've tried to build erlang on a US III machine where I'm currently testing another kernel bugfix for DaveM. This smells pretty much like the same (or another...) US III kernel bug. I'll see what DaveM says to the problem -- Bernd Zeimetz [EMAIL PROTECTED] http://bzed.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Building SPARC32PLUS
Hi, I am building some applications (openoffice.org) using gcc and g++ [EMAIL PROTECTED]:~/vanilla$ gcc --version gcc (GCC) 4.2.3 20071123 (prerelease) (Debian 4.2.2-4) [EMAIL PROTECTED]:~/vanilla$ g++ --version g++ (GCC) 4.2.3 20071123 (prerelease) (Debian 4.2.2-4) When running the file command I have noticed the object files are SPARC e.g. $ file something.o blah ... SPARC $ file everything.so blah -... SPARC32PLUS I assume the shared libs are different because they are linked to SPARC32PLUS files in /usr/lib... is that right? Also I notice that gcc -mcpu=v9 is needed to get object files like SPARC32PLUS. Is that the correct behaviour? I suppose I am wondering why gcc doesn't produce SPARC32PLUS by default. thanks jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
