/srv/irclogs.ubuntu.com/2006/12/20/#ubuntu-ports.txt

=== lamont` [i=lamont@nat/hp/x-f4fcab3cd8b89135] has joined #ubuntu-ports
Dvalinfabbione: around?01:02
fabbioneDvalin: i am now so to speak04:47
Dvalinstill?05:50
Dvalinfabbione: what's the status of gcc 4.1.2 & kernel on sparc at your camp?05:51
fabbioneDvalin: gcc dunno.. what's in the archive...05:51
fabbionekernel we are going for .20 + some patches05:52
Dvalinokay, using 4.1 is no good for kernel it seems here05:53
Dvalin4.0 works fine05:53
Dvalin:/05:53
Dvalinso I blame the compiler05:53
fabbionethe one we are using is good05:53
fabbionei am booting those kernels05:53
Dvalincompiled with gcc 4.1.2?05:58
Dvalinmine will only boot without display05:58
Dvalinbut then again05:59
Dvalinother hardware etc. too05:59
=== lamont [i=lamont@nat/hp/x-afe4774a333de41d] has joined #ubuntu-ports
fabbioneDvalin: compiled with whatever we have in the archive now06:24
Dvalinokay06:25
Dvalinwhich kernel version was that again?06:25
fabbione.19 and .20-rc...06:26
Dvalinokay06:26
DvalinI'll go ahead and try one of those then :)06:38
Dvalinbtw. why is sparc not visible on packages.ubuntu.com?06:39
fabbioneno idea06:40
fabbionei did never used packages.u.c06:40
Dvalinokay06:40
fabbionefile a bug :)06:40
Dvalinnah06:40
DvalinI'm just asking out of curiousity, couldn't care less for myself ;)06:41
Dvalinbtw. there's one thing that puzzles me, why isn't different archs reported on sparc? eg. like sparcv8, sparcv9 etc. as i586, i686 etc. on intel?06:42
fabbioneuhm?06:42
Dvalineg. by 'arch'06:43
fabbioneyeah but where..06:43
Dvalinuhm, in general? by kernel?`:)06:43
fabbioneyou make no sense06:45
fabbionewhere do you want to read that information?06:45
Dvalinhmhm06:45
fabbioneproc/cpuinfo? uname -a ?06:45
Dvalinuname -m for an instance06:46
fabbionebecause you don't need it06:46
fabbionethe kernel is either 32 or 64 bit. all optimizations are autodetected and turned on at boot06:46
fabbioneso there is no point for userland to know06:47
fabbioneand you can still see the hw cap via glibc06:48
Dvalinwhy is there less of a need for it than on x86?06:48
DvalinI'd still say there is a use for userland to know, eg. when building stuff..?06:49
fabbionefabbione@rainy:~$ LD_SHOW_AUXV=1 /lib/libc.so.6 --version  | grep AT_HWCAP06:49
fabbioneAT_HWCAP:    flush stbar swap muldiv v9 v9v06:49
fabbioneno there is no need to know.. how build needs to know what's doing06:49
fabbioneall these extra automatic features have been proven to be a real disaster06:50
Dvalinoh?06:50
fabbionewhen you autodetect something at build time and thenD you distribute a precompiled binary on a machine that does not have that feature it's BA06:58
fabbioneBAD06:58
Dvalinyeah, but that's why you specify the arch of binary ;p06:58
fabbioneDvalin: that's also why stuff works for us but not for you07:06
Dvalinuh08:15
DvalinI don't see the relevance of that08:15
Dvalinactually, AFAIK you build for sparcv8 by default without packages saying anything about it NOT being compatible with sparcv7 which just 'sparc' usually implies ;p08:17

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