**** BEGIN LOGGING AT Sun Nov 01 02:59:56 2009
**** ENDING LOGGING AT Sun Nov 01 04:47:38 2009

**** BEGIN LOGGING AT Sun Nov 01 04:47:58 2009
Nov 01 18:03:28 <jomaster> @eno: are you there? short qestion ;-)
Nov 01 18:09:06 <jomaster> i have to leave soon.
Nov 01 18:59:13 <eno> jomaster: i'm here now
Nov 01 18:59:31 <eno> you can actually leave your question here
Nov 01 18:59:33 <jomaster> sorry, i leave now. perhaps in 3h
Nov 01 18:59:54 <CIA-27> 03bzhou * r10838 10optware/trunk/make/gloox.mk: gloox: 0.9.9.9 -> 1.0
Nov 01 19:00:08 <CIA-27> 03bzhou * r10839 10optware/trunk/make/cherokee.mk: cherokee: 0.99.24 -> 0.99.26
Nov 01 19:00:48 <eno> you can also send email to nslu2-developers
Nov 01 19:01:04 <jomaster> i think you can answer it better.
Nov 01 19:01:27 <jomaster> about busybox for fsg3. (is disbaled cause of build error)
Nov 01 19:02:05 <eno> i admit i haven't digged deep to solve issues for fsg3/fsg3v4
Nov 01 19:02:31 <eno> you're welcome to take a crack if you can replicate the problem
Nov 01 19:02:38 <jomaster> the reason is file route.h in fsg3v4-toolchain is different to route.h in busybox. if i remove this file for busybox-build all works fine
Nov 01 19:02:54 <jomaster> how to add a workaround for this?
Nov 01 19:03:05 <jomaster> i read your post later
Nov 01 19:03:21 <eno> is route.h supposed to be in toolchain?
Nov 01 19:03:33 <jomaster> don't know
Nov 01 19:03:49 <jomaster> currently try for my build-system
Nov 01 19:03:55 <jomaster> su later
Nov 01 19:04:34 <eno> it's in other toolchains as well
Nov 01 19:04:52 <eno> the question is why it is not causing problem for other toolchain
Nov 01 19:05:21 <eno> it may have something to do with searching order and visibility
Nov 01 20:54:24 <Reedy> Hey eno, did you manage to get any further with 9.10?
Nov 01 21:41:44 <eno> Reedy: nslu2 toolchain builds fine on 9.10 as long as you symlinking gcc-3.3 to gcc
Nov 01 21:53:39 <Reedy> Hmm, eno seems to have given up during building the toolchain for me
Nov 01 21:53:59 <Reedy> http://nslu2.pastebin.com/m72d61b1b
Nov 01 22:15:44 <eno> Reedy: I think I've seen that when I was using gcc-4.4
Nov 01 22:15:55 <eno> ls -l /usr/bin/gcc
Nov 01 22:16:02 <eno> what's the output right now?
Nov 01 22:16:20 <eno> and after you symlink to gcc-3.3
Nov 01 22:16:29 <eno> make sure the toolchain build starts from scratch
Nov 01 22:16:42 <eno> by "rm -f toolchain/crosstool/.configured"
Nov 01 22:16:45 <Reedy> oh, wait
Nov 01 22:16:59 <Reedy> I thought you meant symlink gcc-3.3 to gcc
Nov 01 22:17:21 <Reedy> reedy@ubuntu32-esxi:~/slug/optware/nslu2$ ls -l /usr/bin/gcc
Nov 01 22:17:21 <Reedy> lrwxrwxrwx 1 root root 7 2009-10-30 10:47 /usr/bin/gcc -> gcc-4.4
Nov 01 22:17:21 <Reedy> reedy@ubuntu32-esxi:~/slug/optware/nslu2$ ls -l /usr/bin/gcc-3.3
Nov 01 22:17:21 <Reedy> lrwxrwxrwx 1 root root 3 2009-11-01 22:43 /usr/bin/gcc-3.3 -> gcc
Nov 01 22:17:41 <eno> ah no, that's not what we want
Nov 01 22:17:56 <eno> you better reinstall gcc-3.3
Nov 01 22:18:07 <eno> cd /usr/bin; ln -sf gcc-3.3 gcc
Nov 01 22:18:10 <Reedy> 3.3 isnt in the ubuntu feeds... or at least, not the default ones
Nov 01 22:18:33 <eno> ok, that's some problem
Nov 01 22:18:50 <eno> you probably have to get it from older ubuntu feed
Nov 01 22:18:52 <Reedy> was last in dapper
Nov 01 22:19:21 <eno> is there any gcc-3 at all?
Nov 01 22:19:48 <Reedy> theres a 3.4 in debian
Nov 01 22:19:56 <Reedy> so presumably ubuntu has it oo..
Nov 01 22:20:07 <eno> (I was ugrading a few times, that's why I have it)
Nov 01 22:20:41 <Reedy> hmmm
Nov 01 22:20:55 <Reedy> doesnt seem to exist in ubuntu
Nov 01 22:21:25 <eno> that particular problem you have, I actually found a patch that can address that
Nov 01 22:21:40 <eno> but the bad news is there're more error after that
Nov 01 22:21:50 <Reedy> theres 3.4 in jaunty (9.04)
Nov 01 22:21:54 <Reedy> but not in karmic
Nov 01 22:22:01 <Reedy> I could just whack a debian vm up?
Nov 01 22:22:04 <Reedy> Seems its gonna be quicker
Nov 01 22:22:42 <eno> unslung toolchain is too old
Nov 01 22:22:51 <Reedy> hmm
Nov 01 22:22:59 <eno> but we don't have a good way around
Nov 01 22:23:03 <Reedy> worth just trying a different target?
Nov 01 22:23:16 <eno> other target should work fine
Nov 01 22:23:37 <eno> lot of them just download toolchain binary
Nov 01 22:23:42 <Reedy> heh
Nov 01 22:25:23 <Reedy> used sheevaplug..
Nov 01 22:25:29 <Reedy> checking for C compiler default output file name...
Nov 01 22:25:29 <Reedy> configure: error: C compiler cannot create executables
Nov 01 22:25:29 <Reedy> See `config.log' for more details.
Nov 01 22:25:29 <Reedy> make: *** [/home/reedy/slug/optware/sheevaplug/builds/which/.configured] Error 77
Nov 01 22:25:48 <Reedy> Which is the error i was getting a few days ago, but that was a permissions error
Nov 01 22:26:03 <eno> sheevaplug target should use cs08q1armel toolchain
Nov 01 22:26:31 <eno> when you see this kind of error, look inside builds/which/config.log
Nov 01 22:26:39 <eno> and see what's the actual error
Nov 01 22:27:24 <Reedy> configure:2620: /home/reedy/slug/optware/sheevaplug/toolchain/arm-2008q1/bin/arm-none-linux-gnueabi-gcc  -O2   -pipe -I/home/reedy/slug/optware/sheevaplug/staging/opt/include   -L/home/reedy/slug/optware/sh$
Nov 01 22:27:24 <Reedy> ./configure: line 2621: /home/reedy/slug/optware/sheevaplug/toolchain/arm-2008q1/bin/arm-none-linux-gnueabi-gcc: No such file or directory
Nov 01 22:28:03 <eno> sheevaplug should just symlink to cs08q1armel
Nov 01 22:28:21 <eno> we only use sheevaplug for sheevaplug specific packages
Nov 01 22:28:29 <eno> for packages like which, use cs08q1armel
Nov 01 22:28:46 <Reedy> ahh right
Nov 01 22:29:05 <eno> so, "make cs08q1armel-target; cd cs08q1armel; make directories toolchain ipkg-utils"
Nov 01 22:29:25 <Reedy> hmmm
Nov 01 22:29:28 <Reedy> I'd done that
Nov 01 22:29:33 <Reedy> bar the make toolchain
Nov 01 22:29:40 <Reedy> "cd <platform>; make directories ipkg-utils" in the which
Nov 01 22:29:50 <Reedy> *in the wiki
Nov 01 22:29:51 <Reedy> I'll change/update that?
Nov 01 22:30:02 <eno> yes please
Nov 01 22:30:20 <Reedy> its downloading the toolchain now, presumably as a prequisite to building which
Nov 01 22:30:21 <Reedy> ?
Nov 01 22:30:30 <eno> which wiki page are you following?
Nov 01 22:30:50 <Reedy> http://www.nslu2-linux.org/wiki/Optware/AddAPackageToOptware
Nov 01 22:31:53 <eno> alright, I see you've already made the change
Nov 01 22:34:30 <Reedy> target of nslu2 is unslung?
Nov 01 22:34:41 <eno> yes
Nov 01 22:45:24 <jomaster> eno: is it possible to change the search order?
Nov 01 22:49:18 <eno> jomaster: i don't remember whether the search order is specified at toolchain build time, or it can be changed afterwards
Nov 01 22:50:54 <jomaster> ok, i will read about it. at my build system all builds fine without this header-file.
Nov 01 22:52:00 <eno> use /full-path/to/target/gcc -print-search-dirs
Nov 01 22:52:07 <eno> to see the current search order
Nov 01 23:05:56 <Reedy> Yup, eno, cs08q1armel is fine :)
Nov 02 01:23:45 <CIA-7> 03bzhou * r10840 10optware/trunk/make/libelf.mk: libelf: 0.8.12 -> 0.8.13
**** ENDING LOGGING AT Mon Nov 02 02:59:56 2009