/srv/irclogs.ubuntu.com/2005/12/10/#ubuntu-toolchain.txt

=== doko_ [n=doko@dslb-084-059-076-155.pools.arcor-ip.net] has joined #ubuntu-toolchain
=== chmj [n=chmj@dsl-146-190-232.telkomadsl.co.za] has joined #ubuntu-toolchain
fabbioneWO HOOO11:39
fabbioneanother gcc-4.0 regression on sparc11:39
fabbione../../ghc/compiler/ghc-inplace -H16m -O -cpp -fffi -Iinclude  -ignore-package X11 -O -Rghc-timing -fgenerics  -package base -fgenerics -split-objs -hisuf p_hi -hcsuf p_hc -osuf p_o -prof   -c Graphics/X11/Xlib/Misc.hs -o Graphics/X11/Xlib/Misc.p_o  -ohi Graphics/X11/Xlib/Misc.p_hi11:40
fabbionegcc: Internal error: Segmentation fault (program as)11:40
fabbionePlease submit a full bug report.11:40
fabbioneSee <URL:http://gcc.gnu.org/bugs.html> for instructions.11:40
fabbioneFor Debian GNU/Linux specific bug reporting instructions, see11:40
fabbione<URL:file:///usr/share/doc/gcc-4.0/README.Bugs>.11:40
fabbione<<ghc: 296405008 bytes, 62 GCs, 4390005/8691260 avg/max bytes residency (4 samples), 20M in use, 0.01 INIT (0.00 elapsed), 17.04 MUT (84.43 elapsed), 4.34 GC (4.36 elapsed) :ghc>>11:40
dokoisn't that as?11:43
fabbionedunno.. you are the expert :)11:43
dokoyou are the sparc expert :)11:47
fabbionewell that's general toolchain stuff :P11:48
fabbioneseriously.. what should i look for?11:48
fabbioneif it's really as11:50
dokodoes ghc allow you to run gcc with -v ? then you should at least see the as command line, and then determine, if it fails in as or cc111:50
fabbionethen it's binutils fuckage11:50
fabbionei have NO idea11:51
fabbionei can try to do that11:51
fabbioneit fails at 1.6M in the log that's pretty deep in the build11:51
fabbionei will try that asap. thanks11:51
dokodidn't debian experience some problems with ghc lately?11:52
fabbionedunno11:52
fabbionethey did experience glibc problems on sparc11:52
fabbionethat's for sure11:52
fabbioneit didn't even start to build in debian11:53
fabbioneB-D issues11:53
fabbionedoko: is the new gcc-4.0 good to build or should i wait a bit?12:51
dokofabbione: I tested on i386 and amd64, so maybe you want to wait until these succeed on the buildd01:00
fabbioneok01:00
=== jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-toolchain
=== lamont__ [n=lamont@mib.fc.hp.com] has joined #ubuntu-toolchain
dokoinfinity, lamont, lamont__: gcc-opt ping04:37
fabbionedoko: anything that needs to be tuned on sparc?04:39
fabbioneotherwise i am taking off to go to school04:39
dokofabbione: gcc-4.0 did succeed04:40
dokogcj-4.0 as well04:41
fabbioneyup i saw that04:41
dokogcc-3.4 as well04:41
fabbionethey will build "soon"04:41
fabbionei am also scheduling oo204:42
fabbionebut i have to go now04:42
fabbionettyl04:42
dokofabbione: new oo2 upload needed08:06
fabbionedoko: ok08:09
fabbionedoko: when do you plan to upload oo2?08:46
dokouploading ...08:46
fabbioneoh cool08:47
fabbionethanks08:47
dokothe build did succeed on powerpc and amd64, there must be some problem with parallel make, which I didn't see with my testing08:48
fabbioneoh ok08:48
jbaileydoko: Around?12:00
jbaileyI'm curious if you think it's safe to make the biarch amd64 package "libc6-i686" instead of "libc6-i386"12:00
jbaileySince I'm fairly sure that amd64 can support all the i686 instructions including CMOV.12:00

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!