Posts

distcc

Distcc is working. Howerver, I didn't get it working at the beginning. Because I am curious about what messages distccd's pass between themselves. So I fired up wireshark, then I go to sleep. As you would expect, eventually wireshark occupied all free space on /tmp which is also used by distcc to produce object files. And as a consequence, distcc failed. Originally, the distcc run with "--log-level critical", so it sent nothing to syslog. By using this command, you can see what distcc is doing in real time: distccd --verbose --log-stderr --daemon --user distcc --allow 192.168.1.103 --no-detach

I will give up cross compiling KDE

Two posts related to this decision: http://zhllg.blogspot.com/2007/03/rfcpossible-improvements-to-with.html http://zhllg.blogspot.com/2007/03/some-ideas-about-dependrdepend.html I will try distcc.

some ideas about DEPEND/RDEPEND

(zhllg) Is it possible that a runtime dependency is not a build time dependency? or could a package be built without some package, but require it in order to run? (igli) yes (zhllg) igli, any example? (igli) not necessarily required at run time; in any case eg an app that runs a cmd (igli) might not need to be built against the other app (zhllg) oh that is true (igli) synfig has run time deps for i think jpeg and stuff (igli) need to work on ebuild.. :( (zhllg) igli, what about the runtime dependency is a library (igli) usu if it's a dep against a lib, it's compile time (marienz) both. (igli) depends on whether it looks for the .h files (marienz) normally both. (igli) oh sorry, yes runtime as well of course (igli) as lib needed on system when app is running :) doh! (zhllg) then IMHO maybe in that case just specify the dependency in RDEPEND is enough, what do you think? (marienz) you normally need the lib present at build time or the link will fail. (zhllg) yes (igli) yup (igli)

[RFC]possible improvements to --with-sysroot

The following suggestion is based on my understanding of --with-sysroot, if there were any error, please correct me. To my understanding, currently if cross-compile tool chain (including gcc) is configured with --with-sysroot when installing them, then when cross compiling, ld will look for libraries in $SYSROOT/usr/lib and $SYSROOT/usr/local/lib. Wouldn't it be great that we go one step further that we let ld look for libraries in the dir listed in $SYSROOT/etc/ld.so.conf, if this file ever exits? Of course for each entry in $SYSROOT/etc/ld.so.conf, we prefix $SYSROOT to it. Comments are welcomed. Thanks! -- Zhang Le, Robert This is an email I have posted to gcc mailing list.

emerging KDE on loongson

I have got DRI working in Gentoo on loongson. mesa/libdrm/kernel/xorg-server/xf86-video-ati need to be patched in order to achieve this. I have set up a loongson overlay, including the necessary patches. Get it here: http://gentoo.linuxsir.org/download/loongson-overlay.tar.bz2

kgdb and 64bit loongson kernel

The kernel crashed at last. But it didn't drop into gdb. I have set up a breakpoint at panic(), so it is not a panic. My speculation proved wrong, and I have no idea what went wrong here. I will give up for the time being. Gotta read some books and help to make the 32bit loongson port stable.

gorg on loongson box

I have successfully run gorg on my loongson box. Find more info about gorg here: http://gentoo.neysx.org/mystuff/gorg/gorg.xml more info about loongson here: http://en.wikipedia.org/wiki/Loongson