IRC log for #uclibc on 20101123

00:18.48*** join/#uclibc WildPikachu (~nkukard@about/linux/staff/wildpikachu)
00:28.21*** join/#uclibc WildPikahcu_ (~nkukard@dsl-247-39-77.telkomadsl.co.za)
00:40.54*** join/#uclibc xiangfu (~xiangfu@124.205.34.122)
01:10.00*** join/#uclibc WildPikahcu_ (~nkukard@41-133-248-248.dsl.mweb.co.za)
01:11.00*** join/#uclibc WildPikachu (~nkukard@about/linux/staff/wildpikachu)
01:23.35*** join/#uclibc bkuhn (~bkuhn@fsf/director/conservancy.president.bkuhn)
03:25.59*** join/#uclibc tchan (~tchan@lunar-linux/developer/tchan)
03:40.35*** join/#uclibc Whoopie_ (Whoopie@unaffiliated/whoopie)
04:15.59*** join/#uclibc angstrom1 (~mobilgeni@117.192.66.105)
04:46.27angstrom1Thanks folks :). I figured out and enabled those options in the build. Now when I try to run the build, it fails to execute sed. The permissions are correct.                 /bin/bash: /home/linuxsri/Projects/SBC/buildroot-2010.08/output/toolchain/bin/sed: cannot execute binary file
04:46.28angstrom1make: *** [/home/linuxsri/Projects/SBC/buildroot-2010.08/output/build/busybox-1.17.1/.stamp_configured] Error 126
04:53.32*** join/#uclibc antgreen (~user@CPE00222d6c4710-CM00222d6c470d.cpe.net.cable.rogers.com)
05:03.48angstrom1Anyone??
05:43.59*** join/#uclibc saftsack__ (~oliver@p5DDCE5FB.dip.t-dialin.net)
05:57.13*** join/#uclibc fabled (~fabled@mail.fi.jw.org)
06:05.32*** join/#uclibc doc2 (~Dieter@139.12.1.251)
07:01.18speakmantry: file /home/linuxsri/Projects/SBC/buildroot-2010.08/output/toolchain/bin/sed
07:02.39*** join/#uclibc angstrom2 (~mobilgeni@117.192.71.114)
07:35.17*** join/#uclibc kos_tom (~thomas@humanoidz.org)
08:13.27*** join/#uclibc angstrom1 (~mobilgeni@117.192.77.60)
08:22.08CIA-6203vda.linux 07master * r5ab20641d687 10busybox/Makefile: Bump version to 1.18.0
08:22.36CIA-6203vda.linux 07refs/tags/1_18_0 * r5ab20641d687 10busybox/Makefile: Bump version to 1.18.0
08:29.50CIA-6203vda.linux 07master * r6deeded94283 10busybox-website/news.html: Announce 1.18.0
08:44.59CIA-6203vda.linux 071_18_stable * r5ab20641d687 10busybox/Makefile: Bump version to 1.18.0
08:53.09*** join/#uclibc |aks| (~kvirc@mx.3alitydigital.de)
08:56.08*** join/#uclibc doc2 (~Dieter@139.12.1.251)
09:19.48*** join/#uclibc doc2 (~Dieter@139.12.1.251)
09:30.47*** join/#uclibc calculus (~calculus@gentoo/user/calculus)
09:37.10CIA-6203dvlasenk 07master * rfc61b2addfe5 10busybox-website/news.html: mark 1.18.0 as *un*stable
09:42.48CIA-6203dvlasenk 07master * r7b8028ce1055 10busybox-website/news.html: cosmetic fixes in changelog
12:28.35*** join/#uclibc ibot (~ibot@rikers.org)
12:28.35*** topic/#uclibc is discussion of uClibc, Busybox and Buildroot | uClibc 0.9.31 was released 2nd Apr 2010 | busybox 1.17.3 was released 9 October 2010 (unstable busybox 1.18.0) | Buildroot 2010.08 was released 31 August 2010 (2010.11-rc1 on 9 November 2010) | For general setup issues try #elinux or #edev
12:57.19*** join/#uclibc kos_tom (~thomas@humanoidz.org)
13:15.33speakmanShouldn't there be an additional "install" target in packages' Makefiles?
13:16.39speakmanCurrently, binaries are installed in the output/target on the "make" stage, which makes it timeconsuming to rebuild the output/target tree (when finetuning your skeleton for example)
13:20.39gustavozthere is
13:21.15gustavoz$package-install does the trick, of course if you're tweaking and said package was installed it does nothing, but you can $package-uninstall first to force it
13:28.29speakmanIs there a target in top level Makefile to rebuild output/target/ dir?
13:29.27speakmanI just did rm -rf output/target/ and then "make" on top level. The result was a new output/target/ dir with just a minor of all stuff supposed to be there. The skeleton wasn't even copied.
13:30.14kos_tomspeakman: the stamps files related to the installation of packages are not in output/target, so removing output/target just cannot work.
13:32.17gustavozfind output/build -name .stamp_target_installed -exec rm {} \; may work, never tested though
13:32.50dj-deathyou'll miss the libc etc...
13:32.59gustavozoh yes, that's the reason "may work" :)
13:33.20speakmanreally? according to http://buildroot.uclibc.org/buildroot.html#add_packages there should be a $(TARGET_DIR)/$(LIBFOO_TARGET_BINARY): $(LIBFOO_DIR)/$(LIBFOO_BINARY) target?
13:33.27dj-deathI think removing output/build/.root may help
13:33.46dj-deathbut it's going to reinstall staging as well (for the libc part)
13:34.11speakmannope, removing .root didn't do the trick
13:34.15gustavozwhat's the problem with your skeleton? if it's clean enough you may usually just overwrite everything in the target with it
13:35.07speakmangustavoz: that's maybe true, but it's much "cleaner" to have a "install" target in top level Makefile
13:36.54gustavozspeakman: it might be interesting, however i'm interested in doing the toolchain migration ATM :)
13:36.59speakmanif all packages were like the tutorial, removing output/target/ should work. At least for the non toolchain-packages. http://buildroot.uclibc.org/buildroot.html#manual-tutorial
13:37.16speakmantoolchain migration?
13:38.12gustavozspeakman: the manual makefile is the old way of doing packages, we're going away from that
13:38.15speakman(note that there's no libfoo-install target)
13:38.43speakmangustavoz: so what's the plan?
13:39.01gustavozspeakman: autotargets for auto* packages or gentargets for regular makefile
13:39.03speakmansort of liked it... :)
13:39.32speakmanhttp://buildroot.uclibc.org/buildroot.html#generic-tutorial ?
13:39.50gustavozyes
13:41.02gustavozwith the old method you had to do almost everything by hand and duplicated things that are pretty much generic
13:41.17speakmanmay I ask where the "magic" of autopackages happens? like where's the parsing of the Makefile?
13:41.40speakmangustavoz: that's true, at least for packages using autotools.
13:42.14gustavozspeakman: it's the same for generic (non-auto) packages, you don't need to handle the fetching, patching and so on
13:42.55speakmanoh.. it's line 27 i guess; $(eval $(call GENTARGETS,package,libfoo))
13:43.31kos_tomspeakman: "manual packages" no longer exist.
13:43.56kos_tomspeakman: as stated at the beginning of this section, "NOTE: new manual makefiles should not be created, and existing manual makefiles should be converted either to the generic infrastructure or the autotools infrastructure. This section is only kept to document the existing manual makefiles and to help understand how they work."
13:44.02gustavozpart of the toolchain thing i'm doing is getting them away from being manual packages for example
13:45.01kos_tomspeakman: generic and autotargets packages use infrastructure in package/Makefile.{package,autotools}.in
13:45.19speakmankos_tom: you want me to read ALL the documentation? *blush* :)
13:45.22kos_tomgustavoz: is it possible to track your progress on this on some git tree ?
13:45.49kos_tomspeakman: basically, what you want to do is today not possible with the current infrastructure. We need to make further improvements to make this possible.
13:45.54gustavozkos_tom: i'll be uploading the stuff once i finish my regression tests :)
13:46.34speakmankos_tom: you mean remaking the output/target/ ?
13:46.50kos_tomspeakman: yes.
13:47.03kos_tomgustavoz: great. Is the job finished already ?
13:47.40gustavozkos_tom: not yet, done with the support stuff (mpc, mpfr, gmp) and making the toolchain use the new way
13:48.05gustavozkos_tom: next step is moving binutils/gcc to host instead of staging, and then probably converting binutils to a package. gcc might be tricky in that regard.
13:48.49gustavozat the moment everything works even target toolchain
13:49.32*** join/#uclibc mnt_real (~mnt_real@bas9-montrealak-1177755340.dsl.bell.ca)
13:50.25kos_tomgustavoz: so mpc, mpfr and gmp are now installed in $(HOST_DIR), and the toolchain is linked dynamically against it ?
13:50.31kos_toms/it/them/
13:51.36speakmanpriceless bot? :)
13:51.49gustavozkos_tom: yes sir
13:52.04kos_tomgustavoz: awesome!
13:52.16kos_tomgustavoz: so you're using the --rpath trick ?
13:52.52speakmankos_tom and gustavoz: How far is the migration of this "new way" to mainline?
13:52.58gustavozkos_tom: not needed, gcc is hardcoded to find libmpfr/gmp/mpc in the correct path
13:53.13speakmanhttp://wiki.debian.org/RpathIssue
13:53.15kos_tomgustavoz: ah. How ?
13:53.33kos_tomspeakman: yes, rpath on target is incorrect, but rpath on host is ok for what we are doing.
13:53.40speakmanoh i see
13:55.15*** join/#uclibc bkuhn (~bkuhn@fsf/director/conservancy.president.bkuhn)
13:57.06speakmanLooking at the "new way" of doing packages Makefile, there is a LIBFOO_INSTALL_TARGET_CMDS; shouldn't that be enought for a "make install" (or even better; "make image") feature in Buildroot?
13:58.12speakman(another feature I'd like is to see is to split the target filesystem into two filesystem images, but that's another story I guess)
13:58.15kos_tomspeakman: probably. Not sure what's the use case is for such a "make install" target.
13:58.57speakmanto remake the filesystem?
13:59.11speakmanif there has been a change in skeleton e.g.
13:59.57speakmanI remember Axis supported "make images" in their SDK (which worked pretty much as Buildroot does), and I used pretty often.
14:00.56gustavozkos_tom: i'm passing the hostdir for the components and it gets hardcoded in the binaries (--with-mpc=$(MPC_HOST_DIR) and so on)
14:01.11kos_tomgustavoz: ah, ok.
14:01.29gustavozkos_tom: i'm waiting for jacmet to pull the remaining patches for 2010.11 to upload this, or i could just make a new repo
14:01.33speakmanNo more host binaries in staging dir..?
14:01.43kos_tomgustavoz: you can make a separate branch in the same repo.
14:02.01gustavozkos_tom: yes, but i gotta merge first :)
14:02.01kos_tomspeakman: no, we're moving away from that since it's incorrect.
14:02.19kos_tommerge what ?
14:02.21speakmankos_tom: I agree it is
14:02.25gustavozkos_tom: jacmet's changes :)
14:02.54kos_tomgustavoz: not sure to understand. Just base your toolchain changes on the current buildroot master, and put them in a separate branch from you 2011.11-specific fixes.
14:04.03speakmanMay I ask if there's a official roadmap for Buildroot? I'm interrested in the development, but I havn't heard of this new "toolchain migration" :)
14:04.41speakmanIs there any lists of available Buildroot git repositories?
14:05.13speakmanCIA seems to know a few, but won't hand over the list :)
14:07.04gustavozkos_tom: i'll give it a shot, my git-fu isn't top notch :)
14:07.17gustavozshould have branched before
14:07.20kos_tomspeakman: no, we don't have a written roadmap. I've started a wiki, but haven't had the time to migrate contents over it. This would be the good place for this kind of stuff.
14:07.33kos_tomgustavoz: you can create a branch as an afterthought as well.
14:07.51gustavozkos_tom: hmm yeah but i gotta roll back conflicting commits
14:08.03gustavozs/roll/resolve/
14:08.18speakmankos_tom: sounds great! Is there an official project manager for Buildroot currently?
14:08.19kos_tomnot sure what your repo organization is, so a bit hard to help you here :)
14:08.32kos_tomspeakman: yes, Peter Korsgaard (Jacmet on IRC)
14:08.39gustavozkos_tom: i did a pull from master buildroot -> my master, so it's messy :)
14:08.44speakmanThanks! :)
14:08.47gustavozand i've commited to my master
14:08.57kos_tomgustavoz: aah, this is bad.
14:09.13gustavozkos_tom: i'll export the remaining patches, refetch everything and branch there
14:09.30gustavozthat way i can keep my master -> real master
14:10.32speakmanor rename your master, and pull a new master?
14:11.50gustavozit'll be easier to redo so i can branch small fixes for-2010.11 and so on
14:11.58gustavozi'll need multiple branches
14:13.23kos_tomgustavoz: I always have ~10 local branches to do BR development.
14:13.46gustavozkos_tom: i've seen, didn't expect to be doing that much so i didn't branch initially but things changed
14:13.54kos_tomgustavoz: I had a gmp-conversion branch, of which a few commits might be interesting to you (minor cleanups).
14:13.54speakman(maybe you could checkout your current master into a new branch, and then revert your master into origin/master)
14:14.27gustavozi'm just saving the relevant patches, it's easy, i'll git am everything once i'm upstream
14:14.30speakmanbranching is sort of science...
14:14.32kos_tomgustavoz: you can always create a branch for the current commit, and then move back master to the latest commit of the upstream master branch.
14:14.40kos_tomgustavoz: a branch is nothing but a pointer to a particular commit
14:15.00speakmankos_tom: like I just said... :D
14:15.02gustavozkos_tom: gotta do the cleanup to see what's pending for 2010.11 anyway, i'm not that far
14:15.40speakmanIs there at least a roadmap for 2010.11?
14:16.42kos_tomspeakman: 2010.11 is mostly done. rc1 has been released, so nothing spectacular will happen before the release. And the final release should show up in ~one week.
14:17.17gustavozmy pending fixes are mostly build fixes, like the squid one
14:18.08speakmansounds great. It just that it's seems a bit difficult to new people (like me) to know what's going on. Hence my questions :)
14:18.42kos_tomgustavoz: http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=gmp-conversion&id=d4558237e2f1277a21fcf5e4837f5d34d6c8cdcd
14:18.51kos_tomgustavoz: http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=gmp-conversion&id=f239ca52a5999443316c5fbf07903f713edb2fad
14:18.58kos_tomgustavoz: http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=gmp-conversion&id=092311d1f725f114d72c1106e8ded2971480f424
14:19.26gustavozkos_tom: cool, thanks, i'll be merging your mips patches as well
14:19.29kos_tomgustavoz: if you could pick up such clean-ups as part of your work, that'd be great.
14:19.45gustavozkos_tom: sure, that's the idea :)
14:19.45kos_tomgustavoz: ah, I would have preferred to keep working on the MIPS patches as they are definitely not finalized.
14:20.06kos_tomgustavoz: for the gmp-conversion patches, just go ahead. I don't mind if you don't keep the attribution, those are trivial cleanups.
14:20.23gustavozkos_tom: as you wish, o64 is probably the broken puppy you mentioned
14:20.42gustavozkos_tom: wrt to binutils my plan is to just make it a package, shouldn't be an issue.
14:21.08kos_tomgustavoz: yes, good idea. Have you move gmp/mpfr/mpc to package/ as well ?
14:21.24gustavozkos_tom: they were packages before, though manual ones, they're auto now :)
14:21.37kos_tomgustavoz: the issue with binutils/gcc is the version selection. When you are in external toolchain mode and you want binutils and gcc for the target, you don't have the version selection available.
14:21.44kos_tomgustavoz: ah, yes, right they were packages.
14:42.37*** join/#uclibc Skyscraper (5c4d6a90@gateway/web/freenode/ip.92.77.106.144)
14:42.48Skyscraperhello
14:43.27*** join/#uclibc risca (~risca@tappan-125-84.eduroam.liu.se)
15:19.12*** join/#uclibc dj-death_ (~djdeath@ims92-1-88-163-235-97.fbx.proxad.net)
15:19.46*** join/#uclibc gmk_ (~gmk@69.72.137.146)
15:21.11*** join/#uclibc tteras_ (~fabled@mail.fi.jw.org)
15:23.53*** join/#uclibc blindvt_ (~bf@85-127-155-31.dynamic.xdsl-line.inode.at)
15:48.42*** join/#uclibc wash (~wash@149.106.192.131)
16:05.09gustavozkos_tom: http://repo.or.cz/w/buildroot-gz.git/shortlog/refs/heads/toolchain-rework (now with host_dir instead of staging_dir, still testing but works so far)
16:30.13*** join/#uclibc tsukasa (~tsukasa@unaffiliated/tsukasa)
16:33.20kos_tom-       #rm -f $(STAGING_DIR)/usr/bin/{ar,as,ld,nm,objdump,ranlib,strip}
16:33.20kos_tom+       #rm -f $(HOST_DIR)/usr/bin/{ar,as,ld,nm,objdump,ranlib,strip}
16:33.33kos_tomthis is commented out, but I really hope the toolchain installation will never install those files.
16:34.05kos_tomgustavoz: looks good!
16:34.22kos_tomgustavoz: but now that you install the toolchain in HOST_DIR, where do you copy the sysroot from HOST_DIR to STAGING_DIR ?
16:34.26gustavozkos_tom: yeah, i'll do the cleanup later on, there are many of those :)
16:35.09gustavozkos_tom: sysroot is installed in staging from the beginning
16:35.26kos_tomgustavoz: ok, I think we'll want to change this.
16:36.00gustavozkos_tom: probably, it's a work in progress(tm). we'll also want to handle libmudflap since it's installed in host_dir and should be in staging_dir (maybe target_dir too)
16:36.16kos_tomgustavoz: ok.
16:36.58gustavozkos_tom: and the docs, we may finally say "hey put HOST_DIR/usr/bin in your path and build away!"
16:39.32kos_tomgustavoz: that's the goal!
16:39.47kos_tomgustavoz: and also to build a sdk. I will write down the report from the Buildroot Developer Day tonight.
16:39.47gustavozok, gdb needs a fix, testing, fixing...
16:39.57gustavozkos_tom: cool that way i'll know where to head to
16:40.10kos_tomgustavoz: I asked " the issue with binutils/gcc is the version selection. When you are in external toolchain mode and you want binutils and gcc for the target, you don't have the version selection available." 2 hours ago. Do you have an idea on this ?
16:40.59gustavozkos_tom: didn't look into that, but have an idea how to solve it in the future: make gcc/binutils target packages
16:41.32gustavozkos_tom: at the moment binutils/gcc .mk files make both which i don't like that much
16:41.33kos_tomgustavoz: maybe even cross gcc and cross binutils need to be moved into package/ as well.
16:41.41*** join/#uclibc tchan (~tchan@lunar-linux/developer/tchan)
16:42.17gustavozkos_tom: binutils will be a package, i don't see that being a problem and it's next on my list for the rework. gcc might be somewhat spooky to achieve but i'll give it a shot.
16:42.35gustavozkos_tom: mostly because gcc is built a couple of times with uclibc
16:42.47kos_tomgustavoz: yeah, gcc is a complicated beast.
16:43.17*** join/#uclibc roadies (~chrislrob@stun.cmf.nrl.navy.mil)
16:44.02gustavozkos_tom: gdb is another candidate to be a proper package
16:44.12kos_tomgustavoz: yes, definitely.
16:44.33gustavozkos_tom: the main aim should be to just keep toolchain/ for the glue
16:44.39kos_tomgustavoz: and I'd really like to take advantage of this rework effort to clean up the way it interacts with external toolchains as well.
16:45.06roadiesAfter upgrading to Fedora 14 buildroot will not build generating the following error:  Makefile:178: *** mixed implicit and normal rules.  It seems make has changed.  Anyone run into this and a fix?
16:48.26gustavozyay, nothing in staging/usr/lib or bin!
16:49.42Skyscraperdoes anyone know, how to crosscompile perl for MIPS?
16:53.21kos_tomgustavoz: you moved the sysroot to host_dir ?
16:53.28kos_tomSkyscraper: well, just use Buildroot, no ? :-)
16:53.45kos_tomroadies: what is your config ? which package does not build exactly ?
16:54.38gustavozkos_tom: not yet
16:54.59kos_tomgustavoz: oh, ok.
16:55.11gustavozkos_tom: it's still living at staging_dir
16:55.18roadieskos_tom:  was trying to build release 2010_08 but now trying the release candidate
16:56.00roadieskos_tom: it appears to be running without failure so far....
16:56.06gustavozkos_tom: oh, yeah, wrong wording on my part "empty staging/lib and staging/usr/bin" (not usr/lib) hehe
16:56.50gustavozkos_tom: no host crap actually :)
16:58.42kos_tomroadies: well, "buildroot fails too build" is far too unprecise to be able to help. There are hundreds of packages and hundreds of configurations in Buildroot.
16:59.14kos_tomroadies: but your problem is related to the fact that Fedora 14 uses make 3.82, and yes 2010.11-rcX have fixes for this.
16:59.40roadieskos_tom:  yeah sorry so note, the real problem I think is with the kernel itself, aka one fix for this was the main Makefile in the linux sub-directory.  The downside to this is one can't build a prior linux release...say....2.6.19.1
17:01.13roadieskos_tom:  thanks its what I though, aka change with make which is a bummer cause even though buildroot allows building prior linux it wont work cause of make update
17:01.15kos_tomroadies: yes. That's a known problem with make 3.82. Everybody is wondering why they broke the compatibility so quickly.
17:01.57roadieskos_tom: they did that to drive struggling fools like me up the wall... *sigh*
17:02.10roadies:-D
17:03.26gustavozkos_tom: the intention of having a sysroot copy in host_dir is to be able to "pack a toolchain" so to speak right?
17:05.08kos_tomgustavoz: yes. But the intention is to compile/install the sysroot in host_dir, and *then* copy it to staging_dir, similarly to what we do with external toolchain and crosstool-ng toolchains.
17:06.03gustavozkos_tom: so basically build a $(HOST_DIR)/usr/mips-xxxx/sysroot directory in it to avoid overwriting host files?
17:06.14gustavoz(or some other dir that's already been thought of)
17:10.15kos_tomgustavoz: exactly.
17:44.35*** join/#uclibc y_morin (~ymorin@ARennes-256-1-75-87.w90-32.abo.wanadoo.fr)
18:08.51*** join/#uclibc trem (~trem@mol92-1-81-57-136-23.fbx.proxad.net)
18:34.18*** join/#uclibc Artemys (~quassel@stp25-1-82-225-18-227.fbx.proxad.net)
19:22.09*** join/#uclibc Orphis_ (~quassel@belgarath.moomoocamp.net)
19:40.48kos_tomtrem: hello
19:41.08tremkos_tom: hello
19:45.47*** join/#uclibc rellig (~rellig@vs1191017.vserver.de)
19:57.10*** join/#uclibc gustavoz (~gustavoz@host145.190-31-135.telecom.net.ar)
20:05.35*** join/#uclibc rellig (~rellig@vs1191017.vserver.de)
20:06.02y_morinkos_tom, trem: hello!
20:06.03y_morinwants to play also!
20:06.23tremthat's a new game
20:06.43kos_tomtrem: I've push a fix to the for-2011.02/boards-cleanup branch that so that with minimal kernel configs, it doesn't hang asking hundreds of questions.
20:07.15tremkos_tom: I haven't forget the sh4 config, but my box don't want to boot
20:34.19*** join/#uclibc risca (~risca@h241n2-n-a31.ias.bredband.telia.com)
20:46.32*** join/#uclibc wash (~wash@149.106.192.131)
20:48.23*** join/#uclibc Orphis (~quassel@belgarath.moomoocamp.net)
21:08.13kos_tomJacmet: around ?
21:08.19kos_tomtrem: ah, hardware problem ?
21:08.49kos_tomI am very stupid, I removed the few slides I prepared for the Buildroot Developer Day.
21:09.09tremkos_tom: I don't understand, grub tell me "error 18"
21:09.22tremkos_tom: I've just removed some old kernel ....
21:22.13*** join/#uclibc Orphis (~quassel@belgarath.moomoocamp.net)
21:28.42y_morinkos_tom: nice report! :-)
21:29.09kos_tomy_morin: I hope I didn't miss anything important.
21:30.39y_morinkos_tom: not that I could notice.
21:30.50y_morins/not/none/
21:43.20*** join/#uclibc trem_ (~trem@mol92-1-81-57-136-23.fbx.proxad.net)
21:47.56*** join/#uclibc dantje (~dvg@HSI-KBW-091-089-103-221.hsi2.kabelbw.de)
22:31.01tremnite all, sweet dreams
22:36.01*** join/#uclibc khem (~khem@99-57-141-118.lightspeed.sntcca.sbcglobal.net)
22:54.25*** join/#uclibc hgb (~hgb@tussi.moria.no)
23:40.57*** join/#uclibc hgb (~hgb@tussi.moria.no)
23:53.02*** join/#uclibc WildPikachu (~nkukard@about/linux/staff/wildpikachu)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.