**** BEGIN LOGGING AT Sun Jun 15 02:59:56 2008 Jun 15 04:36:45 03bzhou * r8495 10optware/trunk/ (4 files in 2 dirs): native gcc: moved libc files into libc-dev ipk - this way gcc and libc-dev can be from diff feeds Jun 15 04:38:20 03bzhou * r8496 10optware/trunk/make/libc-dev.mk: libc-dev: added missing description Jun 15 05:48:35 03bzhou * r8497 10optware/trunk/make/libc-dev.mk: libc-dev: leave c++ headers in gcc Jun 15 06:04:06 03bzhou * r8498 10optware/trunk/make/gcc.mk: native gcc: only delete /opt/lib/libstdc++ with glibc **** ENDING LOGGING AT Sun Jun 15 08:48:02 2008 **** BEGIN LOGGING AT Sun Jun 15 08:53:16 2008 **** ENDING LOGGING AT Sun Jun 15 08:55:10 2008 **** BEGIN LOGGING AT Sun Jun 15 09:03:21 2008 Jun 15 10:12:54 Does chroot work for anyone on SlugOS/LE ? Jun 15 10:13:25 (it works fine on slugos/be, I want to know if it works for anyone on slugosle, cause I'm getting "Illegal Instruction" for both the busybox and coreutils versions of chroot on LE) Jun 15 12:54:33 03oleo * r8499 10optware/trunk/ (make/transmission.mk sources/transmission/transmissiond.c): transmission: 1.21-r6098->1.22-r6196 Jun 15 15:23:05 03bzhou * r8500 10optware/trunk/platforms/toolchain-cs05q3armel.mk: cs05q3armel: set TARGET_LIBC_LIBDIR for libc-dev Jun 15 15:29:41 hi all Jun 15 15:29:52 what is, on debian nslu, the final runlevel? Jun 15 15:45:35 03bzhou * r8501 10optware/trunk/make/hdparm.mk: hdparm: 8.7 -> 8.8 Jun 15 15:49:03 03bzhou * r8502 10optware/trunk/make/ctrlproxy.mk: ctrlproxy: 3.0.6 -> 3.0.7 Jun 15 18:03:35 03bzhou * r8503 10optware/trunk/make/file.mk: file: rid of warning for native build Jun 15 19:12:26 HardDisk_WP: should be in /etc/inittab right? Jun 15 19:13:55 RobNC, found it out already... Jun 15 19:13:57 thx anyway Jun 15 19:14:15 HardDisk_WP no problem, should be 5 right? Jun 15 19:15:12 no idea about that, but I found out what my original problem was Jun 15 19:15:24 thought the nslu was in wrong init level Jun 15 19:15:35 03bzhou * r8504 10optware/trunk/make/ipkg-utils.mk: ipkg-utils: native_shell.patch applies when native build Jun 15 19:15:36 but in reality there just was a typo in network/interfaces Jun 15 19:16:37 Ah I see... Jun 15 19:17:19 03bzhou * r8505 10optware/trunk/platforms/toolchain-openwrt-ixp4xx.mk: toolchain-openwrt-ixp4xx: setup native toolchain for optware Jun 15 19:19:17 anyone know if slugimage does the conversion for apex for LE slugos? I.e., I want to replace apex and redboot from slugosle custom build. Or is it even necessary? Jun 15 19:23:33 03bzhou * r8506 10optware/trunk/make/optware-devel.mk: optware-devel: adds binutils, libc-dev, gcc if available Jun 15 19:34:29 reason I'm asking regarding slugimage is as follows. If I build "slugosle", the kernel and ramdisk (Flashdisk) is already LE, so is there a need to specify that in slugimage for packing the image? Jun 15 20:27:28 rwhitby: your request to re-test with new apex-1.5.14 seems to now include the "init=/linuxrc" appended to APEX env variable "cmdline". Jun 15 21:12:41 hi all, Jun 15 21:12:58 how do i compile a kernel module for optware? **** BEGIN LOGGING AT Sun Jun 15 21:17:26 2008 Jun 15 22:39:25 zouzou: this depends on which optware target platform Jun 15 22:39:46 mss2 Jun 15 22:39:53 for unslung, slugos, and openwrt-ixp4xx, optware does not build kernel modules Jun 15 22:40:30 for MSS II, see make/mssii-kernel-modules.mk Jun 15 22:40:57 do you have cross compilation environment for mssii? Jun 15 22:41:04 nop Jun 15 22:41:30 so you want to try native build? Jun 15 22:41:39 yeah Jun 15 22:42:07 i just fixed some problem of the native toolchain yesterday Jun 15 22:42:26 haven't got around to setup native optware build environment yet Jun 15 22:43:05 so that means i can't? Jun 15 22:44:11 i only tried cross build so far, which is pretty easy Jun 15 22:44:34 easy enough that I do not want to try native build :-) Jun 15 22:45:24 ok, i have never done cross build, is there an easy to follow howto for cross building? Jun 15 22:46:35 http://www.nslu2-linux.org/wiki/MSSII/HomePage Jun 15 22:47:18 see the section starts with "to build optware ipkg for it" Jun 15 22:48:17 for kernel, use mssii as optware target, in the place of cs05q3armel Jun 15 22:48:53 ok, the thing is that the specific module i want is nowhere to be found in the optware folder (bridge module) Jun 15 22:49:39 is that module supported by 2.6.12.6? Jun 15 22:50:05 yeah, i found it in the kernel image i downloaded from kernel.org Jun 15 22:50:14 the same version Jun 15 22:50:24 if so, you just need to change the sources/mssii-kernel-modules/defconfig Jun 15 22:51:17 and 'make mssi*modules-ipk'? Jun 15 22:51:25 this sounds too easy :P Jun 15 22:52:23 yes, "make mssii-kernel-modules-ipk" Jun 15 22:52:45 or even "make kernel-modules-ipk" Jun 15 22:53:02 the modules will be in the same folder, right? Jun 15 22:53:12 same folder i run command from, that is Jun 15 22:53:30 the built modules will be in optware/mssii/builds/kernel-modules Jun 15 22:53:44 the built ipk's will be in optware/mssii/builds/ Jun 15 22:54:09 you need to be in optware/mssii to run the make command Jun 15 22:55:19 send your new defconfig to either MSS forum or nslu2-linux yahoogroups Jun 15 22:55:33 and i can integrate it in the feed Jun 15 22:56:22 OK, will do Jun 15 22:56:41 will send it after i test it Jun 15 23:05:02 eno: doing 'make cs05q3armel-target' is spitting this error, optware/toolchain/armv5b-softfloat-linux/gcc-3.3.5-glibc-2.2.5/bin/armv5b-softfloat-linux-gcc: Command not foun Jun 15 23:05:05 is it ok? Jun 15 23:07:11 that's fine, ignore it for now Jun 15 23:07:19 ok Jun 15 23:14:18 03bzhou * r8507 10optware/trunk/make/gcc.mk: native gcc: skip gcc.mk if gcc is not in the feed Jun 15 23:14:49 eno: i am in ~/optware/sc05q3armel/ , and when i type 'make *mssii-*kernel-modules-ipk' , it returns : make: *** No rule to make target Jun 15 23:15:35 i also tried int make/ Jun 15 23:16:19 what am i doing wrong? Jun 15 23:16:26 cs05q3armel, not sc05q3armel Jun 15 23:16:41 codesourcery 2005q3 Jun 15 23:16:58 yes, it was typo Jun 15 23:17:03 sorry, Jun 15 23:17:41 have you done "make directories ipkg-utils toolchain" ? Jun 15 23:17:50 yes, Jun 15 23:18:04 in fact, when i did make nmap, it worked Jun 15 23:19:01 it's just the kernel-modules that is not working Jun 15 23:20:33 ok, the first few lines of make/mssii-kernel-modules.mk skip the whole .mk if OPTWARE_TARGET is not mssii Jun 15 23:21:04 so, to build kernel for mssii, you need to use mssii as the target name Jun 15 23:21:33 cd optware; make mssii-target; cd mssii; make directories ipkg-utils toolchain Jun 15 23:21:56 then "make kernel-modules-ipk" should work Jun 15 23:22:55 ok, thanx, and sorry to keep buggin you ;) Jun 15 23:24:09 so if get it correctly, i could use cs05q3armel for packages and mssii for kernel modules? Jun 15 23:24:42 right, cs05q3armel user land packages are shared among a couple Orion devices Jun 15 23:25:22 that's the reason we moved MSS II specific ipk's to mssii Jun 15 23:26:07 so that means the howto in mssii homepage isn't necessarily correct Jun 15 23:26:33 feel free to improve the wiki page Jun 15 23:27:51 ok Jun 15 23:30:15 are you planning to have the mssii platform exclusively seperate from the sc05q3armel? Jun 15 23:30:58 what do you mean "exclusively separate"? Jun 15 23:31:33 i mean packages built on cs05q3armel won't work on mssii after the full move? Jun 15 23:32:57 the move (separation) happened months ago Jun 15 23:33:15 cs05q3armel and mssii feed use the same toolchain Jun 15 23:33:58 so packages built on cs05q3armel works fine on mssii Jun 15 23:34:09 oh ok, just wanted to make sure before i change anything 'cs05q3armel' to 'mssii' on the wiki Jun 15 23:34:26 please don't do that Jun 15 23:35:00 you can add something like "for kernel image and modules, use mssii as optware target" Jun 15 23:35:02 ok, then i'll just add that the kernel part needs a mssii platfrom Jun 15 23:35:15 yeah Jun 15 23:35:17 yep Jun 15 23:35:24 thanx for the clarification Jun 15 23:35:50 sorry about the confusion, but practically this works pretty well Jun 15 23:36:50 we also have kernel feed for qnap ts-x07 and freecom dt2 thanks to this separation Jun 15 23:44:35 oh i c Jun 15 23:48:37 i get this error after uning make directories toolchain ipkg-utils http://pastebin.com/m620dcd77 Jun 15 23:48:51 do i need an older gcc? Jun 16 00:59:07 zouzou: "make directories toolchain ipkg-utils" should be done in optware/mssii Jun 16 00:59:35 anyone here in charge of slugos build repository? Possible bug with slugos and ipkg - ipkg is only configured for latest (4.10-alpha) packages, but I installed 4.10-alpha a few days ago and it seemed to have packages that are now not available. Jun 16 00:59:55 when you do "make toolchain" in optware, it is building cross toolchain for unslung Jun 16 01:29:15 RobNC: there is something wrong with the unstable slugos feed. especially the LE feed. Jun 16 01:29:21 the stable feeds are fine Jun 16 01:30:57 rwhitby: this is BE. Jun 16 01:31:19 which packages are missing? Jun 16 01:31:38 i.e., smb, ntp etc. Jun 16 01:32:48 indeed they are. Jun 16 01:34:08 in /etc/opkg/cross-feed.conf I added: "src/gz crossbeta http://ipkg.nslu2-linux.org/feeds/slugosbe/cross/4.8-beta" Jun 16 01:34:09 but I don't feel this should have been necessary, and I may have messed up some things. I believe I can undo the mess though. **** ENDING LOGGING AT Mon Jun 16 01:34:15 2008 **** BEGIN LOGGING AT Mon Jun 16 01:34:44 2008 Jun 16 01:35:28 it shouldn't have been necessary - the unstable feed is broken - we've got some build problems and that's stopping the rest of the feed being populated Jun 16 01:35:47 rwhitby: thanks for confirmation it's broken. AH I see... Jun 16 02:51:47 03bzhou * r8508 10optware/trunk/platforms/toolchain-cs05q3armel.mk: cs05q3armel: native toolchain setup Jun 16 02:52:37 03bzhou * r8509 10optware/trunk/platforms/toolchain-cs06q3armel.mk: cs06q3armel: native toolchain setup **** ENDING LOGGING AT Mon Jun 16 02:59:57 2008