**** BEGIN LOGGING AT Wed Oct 18 02:59:56 2006
Oct 18 06:05:16 <CIA-8> 03bzhou * r4255 10optware/trunk/make/swi-prolog.mk: swi-prolog: upstream upgrade to 5.6.22
Oct 18 08:02:23 <barnseenio> [g2]: problems then?
Oct 18 08:02:52 <[g2]> barnseenio, a configure issue
Oct 18 08:03:00 <barnseenio> u ran the autogen.sh ?
Oct 18 08:03:10 <[g2]> yup
Oct 18 08:03:46 <[g2]> that's on a sarge native release
Oct 18 08:03:59 <barnseenio> you dont have an OPENSSL env var or something?
Oct 18 08:04:12 <[g2]> nope
Oct 18 08:04:27 <[g2]> it's not much more than a debootstrapped sarge
Oct 18 08:04:31 <barnseenio> try --without-openssl
Oct 18 08:06:07 <[g2]> checking for statvfs... ok
Oct 18 08:06:07 <[g2]> ./configure: line 21552: syntax error near unexpected token `OPENSSL,'
Oct 18 08:06:07 <[g2]> ./configure: line 21552: `      PKG_CHECK_MODULES(OPENSSL, openssl,'
Oct 18 08:07:00 <[g2]> that's a configure --without-openssl
Oct 18 08:08:19 <barnseenio> and do you have openssl installed?
Oct 18 08:08:37 <[g2]> yes
Oct 18 08:08:47 <[g2]> there's no -dev package, just the base
Oct 18 08:09:01 <barnseenio> dont you need the headers?
Oct 18 08:10:36 <[g2]> I'm guessing there's not enough of a header set to include a -dev package
Oct 18 08:10:41 <[g2]> dpkg -l | grep openssl
Oct 18 08:10:41 <[g2]> ii  openssl        0.9.7e-3sarge1 Secure Socket Layer (SSL) binary and related
Oct 18 08:11:57 <barnseenio> apt-get install libssl-dev
Oct 18 08:11:58 <barnseenio> ?
Oct 18 08:12:37 <barnseenio> i dont know, your the expert ;-)
Oct 18 08:13:13 <barnseenio> it also says it has dependencies on
Oct 18 08:13:14 <barnseenio> Dependencies ¶
Oct 18 08:13:14 <barnseenio> libsigc++ >= 2.0.x 
Oct 18 08:13:15 <barnseenio> libcurl >= 7.12.x 
Oct 18 08:38:45 <[g2]> barnseenio hey that's a good tip :)
Oct 18 08:39:14 <[g2]> trying again with libssl-dev
Oct 18 08:43:34 * barnseenio rocks!
Oct 18 08:45:07 <[g2]> barnseenio is THE MAN!
Oct 18 08:45:41 <[g2]> unless of course he A WO-MAN
Oct 18 08:50:37 <barnseenio> any progress?
Oct 18 08:52:18 <[g2]> barnseenio sorry, got distracted for a minute (./configure running again)
Oct 18 08:54:03 <[g2]> barnseenio same deal :(
Oct 18 08:54:13 <barnseenio> ugg
Oct 18 08:54:18 <[g2]> barnseenio one minute
Oct 18 08:54:32 <[g2]> I'll try the --without-openssl
Oct 18 08:58:46 <[g2]> barnseenio same 'ol same 'ol
Oct 18 09:01:16 <barnseenio> what do you suggest?
Oct 18 09:02:45 <barnseenio> are you sure you ran the autgen first?
Oct 18 09:02:52 <barnseenio> *./autogen.sh 
Oct 18 09:02:55 <barnseenio> -*
Oct 18 09:08:15 <barnseenio> [g2]: 
Oct 18 09:09:38 <[g2]> barnseenio yes I re-ran ./autogen.sh
Oct 18 09:10:21 <[g2]> that was my distraction, I re-ran autogen, but didn't start the configure
Oct 18 09:11:03 * [g2] rembers to at ; or && to do both commands
Oct 18 09:11:17 <[g2]> wow... typing is starting off bad today
Oct 18 09:11:32 * [g2] remebers to add ; or && to do both commands
Oct 18 09:11:52 <barnseenio> well, i dont know dude, you are the expert. that (although many other problems were encountered) didnt happen for me
Oct 18 09:25:39 <[g2]> barnseenio ok. I'm gonna keep it on the back-burner
Oct 18 09:26:28 <[g2]> right now I'm testing  2.6.18 with the new non-Intel driver
Oct 18 09:26:41 <barnseenio> ok well, thanks anyway
Oct 18 09:26:56 <barnseenio> im sure i'll get that fucker built before 2007
Oct 18 09:26:56 <[g2]> barnseenio, thank-you
Oct 18 09:27:07 <[g2]> LOL
Oct 18 09:27:51 <[g2]> so my short list is 2.6.18 and testing, I'd like to try Etch on the Loft, then libtorrent on Etch
Oct 18 09:28:30 <barnseenio> im going to try the steps outlined in here http://www.nslu2-linux.org/wiki/DebianSlug/CrossCompiling pointed out by eno 
Oct 18 09:35:15 <[g2]> barnseenio that's a good plan. I think dyoung may have an update on the cross proceedure
Oct 18 09:45:19 <barnseenio> [g2]: any opinions on scratchbox?
Oct 18 09:46:24 <[g2]> barnseenio I've never used it. I liked their doc's like about 3 years ago
Oct 18 09:46:58 <[g2]> they clearly understood the problems envolved, but ARM support back then was lacking
Oct 18 09:47:15 <[g2]> barnseenio are you familar with the OSD ?
Oct 18 09:47:33 <barnseenio> nope
Oct 18 09:48:04 <[g2]> Neuros the company makes the OSD which is beta/gamma now
Oct 18 09:48:18 <[g2]> it's kinda like an open TIVO
Oct 18 09:48:30 <barnseenio> mythtv ?
Oct 18 09:48:40 <[g2]> except the codecs and some of the BSP which is TI encumbered
Oct 18 09:49:23 <[g2]> anyway, there are a few devs running scratchbox for that which is ARM926-EJS (plus DSP)
Oct 18 09:49:51 <[g2]> they've been trying to talk me into running scratchbox (but I'm pretty entrenched in OE now)
Oct 18 09:50:38 <barnseenio> i see, well the attraction for me is that with it being in a chroot, the libtorrent shuold have no choice but to run the arm compilers, atm for me it seems to be ignore me, and churning out x86 binaries
Oct 18 09:50:44 <[g2]> OE builds for all the major platforms I'm running (IXP4xx, EP93xx, PXA27x, nslu2-linux, cirrus, and openezx
Oct 18 09:51:25 <[g2]> barnseenio compiling native versus scratchbox shouldn't be any different
Oct 18 09:51:50 <[g2]> I'm guessing it's a versioning thing with the autotools
Oct 18 09:51:57 <[g2]> or a bug
Oct 18 09:52:15 <barnseenio> dunno, as i said .configure and make run for me
Oct 18 09:52:29 <barnseenio> but it spits out x86 binaries no matter what i try and tell it
Oct 18 09:52:57 <barnseenio> i was considering linking my g++ to arm-linux-g++ but my friend tells me it'll bring me bad karma for years
Oct 18 09:53:09 <[g2]> heh
Oct 18 09:53:12 <[g2]> LOL
Oct 18 09:53:50 <[g2]> there's actually a commandline-shell package for OE
Oct 18 09:54:22 <[g2]> it'll setup the cross environment to look like a normal one from the command line
Oct 18 09:54:39 <[g2]> however you still have the issue of any execution issues
Oct 18 09:55:10 <[g2]> which scratchbox handles by the behind the scene go run-it-on-the-traget concept
Oct 18 09:55:30 <barnseenio> ugg, to a linux idiot like me, this is painful
Oct 18 09:59:22 <[g2]> it's pain with a purpose
Oct 18 09:59:43 <[g2]> the problem is dev's don't consider cross-development
Oct 18 10:00:02 <[g2]> they think everything is 'native' in general
Oct 18 10:00:16 <[g2]> unless you're a kernel hacker or something like that
Oct 18 10:00:42 <barnseenio> im sure there are reasons, however i seem to have all the component parts - some source, some cross compilers, the knowledge that this has all been done before - yet still i cant 'make it work'
Oct 18 10:01:10 <[g2]> right I really know the feeling
Oct 18 10:02:12 <barnseenio> each time i explain the problem to someone, they either suggest a different bunch of cross compilers, another undocumented command line parameter to ./configure, or use of some magic dust
Oct 18 10:02:19 <[g2]> I spent the good part of a year working with all the other nslu2-linux devs getting all kinds of stuff working natively/cross etc...
Oct 18 10:02:53 <barnseenio> i can imagine the problems you have encountered far supercede my frustrations building one ultimately uneccessary package!
Oct 18 10:04:33 <[g2]> I've been having quite a good time, although it is maddening at time
Oct 18 10:04:52 <[g2]> I'm more trying to frame the problem space
Oct 18 10:05:10 <[g2]> it's a little like world hunger, but not as serious
Oct 18 10:05:18 <barnseenio> ;-)
Oct 18 10:05:30 <[g2]> the "solution" seems easy.
Oct 18 10:05:35 <[g2]> just feed everybody
Oct 18 10:05:45 <barnseenio> my frustrations are mainly born from what i do not yet know, rather than my ability to develop a solution
Oct 18 10:06:31 <[g2]> exactly, and I'm trying to help you understand things to achive your ultimate goal of a ported package
Oct 18 10:07:57 <barnseenio> yknow that packages i install using apt, who builds those (for ARM) and adds them to the 'authorised' debian package list
Oct 18 10:28:31 <[g2]> barnseenio if your sources.list is pointing the the Debian repos then that's where they come from
Oct 18 10:29:05 <barnseenio> no sorry, i meant which individuals build these packages?
Oct 18 10:29:13 <barnseenio> ppl from projects such as nslu2?
Oct 18 10:29:22 <[g2]> no the Debian project
Oct 18 10:29:29 <[g2]> for ARM LE right ?
Oct 18 10:29:36 <barnseenio> yes
Oct 18 10:29:40 <barnseenio> volunteers?
Oct 18 10:29:49 <barnseenio> or debian is a sponsored project?
Oct 18 10:29:54 <barnseenio> (excuse my ignorance)
Oct 18 10:30:40 <[g2]> debian is a volunteer project there are over 1000 registered devs
Oct 18 10:31:01 <[g2]> and the process takes forever now (a year or two)
Oct 18 11:24:47 <likewise> [g2]: pong
Oct 18 11:24:55 <[g2]> likewise pong
Oct 18 11:25:12 <[g2]> likewise are your running the 46x ?
Oct 18 11:25:20 <likewise> [g2]: nope
Oct 18 11:25:29 <likewise> [g2]: are you yet?
Oct 18 11:25:46 <[g2]> no, but if you've got one I'll test it :)
Oct 18 11:26:07 <[g2]> likewise are you running the open drivers yet ?
Oct 18 11:26:42 <likewise> [g2]: I was planning to work on that this week, but I am now testing an FPGA upload via ixp425 GPIO to a Stratix.
Oct 18 11:27:05 <likewise> [g2]: I would start from my 2.6.17 to 2.6.18 from OE
Oct 18 11:27:21 <[g2]> 2.6.18 in the repo is working
Oct 18 11:27:38 <[g2]> I've three issues on my punchlist
Oct 18 11:27:49 <likewise> [g2]: yes, I just wanted to see that confirmed on my board, and learn the topics involved.
Oct 18 11:27:59 <likewise> [g2]: punch me :-)
Oct 18 11:28:10 <[g2]> 1) pasting in some glue for the EEPROM macs to the driver
Oct 18 11:28:30 <[g2]> 2) I see error msgs about the Redboot partition table
Oct 18 11:28:44 <[g2]> 3) jffs2 seems unhappy, but I think that's a config thing
Oct 18 11:28:52 <[g2]> are you running BE or LE
Oct 18 11:28:56 <likewise> 2) exactly what error? the "does not occupy full erase block"   'error'?
Oct 18 11:29:02 <likewise> BE
Oct 18 11:32:10 <blaster8> The 0.2.1 driver contains fixes for 465 boards, it's included in the latest kernel SVN versions
Oct 18 11:35:04 <[g2]> likewise these http://pastebin.ca/208072
Oct 18 11:38:32 <likewise> 0x00000050-0x00000850   <<--- surely endianess problem. 0x50000000 is flash base memory.
Oct 18 11:41:26 <blaster8> looks like bad endianness to me
Oct 18 11:43:10 <likewise> [g2]: best guess: your redboot has different endianess than the kernel
Oct 18 11:44:20 <[g2]> blaster8 likewise yeah RedBoot is BE and the machine is running LE
Oct 18 11:44:33 <[g2]> that's works fine in 2.6.16
Oct 18 11:44:45 <[g2]> no error messsages
Oct 18 11:44:47 <blaster8> I took out a patch about redboot endianness
Oct 18 11:44:58 <blaster8> but that was because it seemed to be included in mainline
Oct 18 11:46:37 <[g2]> 11-mtdpart-redboot-config-byteswap.patch ?
Oct 18 11:46:40 <blaster8> yes
Oct 18 11:46:46 <blaster8> just checking now
Oct 18 11:47:56 <blaster8> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;h=73ed9a86cd77b6a3b46beec8d353ac3b0d4f50c1;f=drivers/mtd/redboot.c
Oct 18 11:48:19 <blaster8> aah
Oct 18 11:48:39 <blaster8> ok 11-mtdpart-redboot-config-byteswap.patch needs to be restored
Oct 18 11:48:48 <blaster8> the date gives it away
Oct 18 11:48:49 * [g2] already building
Oct 18 11:52:06 <blaster8> I'll commit back to SVN now - we need to send this upstream if it fixes your problem
Oct 18 11:52:28 <[g2]> blaster8 Ok it's better now, but not 100%
Oct 18 11:52:38 <blaster8> ? pastebin?
Oct 18 11:53:01 <[g2]> do you want the full thing or just the cfi section ?
Oct 18 11:53:15 <blaster8> the errors will do
Oct 18 11:53:23 <[g2]> I think this we'll fix my jffs2 problem
Oct 18 11:53:41 * [g2] will be quite happy about that
Oct 18 11:53:54 <blaster8> definitely need to send it upstream
Oct 18 11:54:37 <[g2]> http://pastebin.ca/208095
Oct 18 12:05:09 <blaster8> [g2]: what is the output of fis list in redboot?
Oct 18 12:06:03 <blaster8> I'm just wondering what the difference is between the NSLU2, where this works fine, and the Loft
Oct 18 12:06:24 <[g2]> http://pastebin.ca/208105
Oct 18 12:06:36 <[g2]> blaster8 this works fine on 2.6.16
Oct 18 12:06:50 <[g2]> it's a 2.6.16 -> .18 issue
Oct 18 12:07:31 <[g2]> blaster8 it appears the first 14 partition are being considered for some reason
Oct 18 12:07:46 <[g2]> all the ""
Oct 18 12:08:21 <blaster8> What first 14 partitions?
Oct 18 12:08:21 <blaster8> where are they coming from?
Oct 18 12:08:21 <likewise> [g2]: you should consideren 2.6.17 then...
Oct 18 12:08:42 <[g2]> likewise I've got 2.6.18 just about fully running except for this issue and pulling the MACs from eeprom
Oct 18 12:09:04 <[g2]> this is a trivial problem really
Oct 18 12:09:37 <blaster8> [g2]: do you have a working 2.6.16 source tree around?
Oct 18 12:09:46 <[g2]> blaster8 sure
Oct 18 12:10:14 <blaster8> can you diff the drivers/mtd/redboot.c file between the latest 2.6.18 and 2.6.16
Oct 18 12:10:26 <[g2]> sure
Oct 18 12:12:15 <[g2]> http://pastebin.ca/208110
Oct 18 12:13:05 <[g2]> <               if (buf[i].name[0] == 0xff) {
Oct 18 12:13:05 <[g2]> <                       i = numslots;
Oct 18 12:13:05 <[g2]> <                       break;
Oct 18 12:13:05 <[g2]> <               }
Oct 18 12:13:06 <blaster8> ok, that change is supposed to remove kernel warning, but it actually causes a whole load of them in my tree
Oct 18 12:13:22 <blaster8> sorry, the first bit of the diff
Oct 18 12:13:28 <blaster8> didn't spot that second it
Oct 18 12:14:44 <blaster8> hmm
Oct 18 12:16:29 <blaster8> hack-of-the-day time :)
Oct 18 12:17:04 <blaster8> can you run up 2.6.18 with the redboot.c from 2.6.16
Oct 18 12:18:23 <blaster8> I'm wondering if Redboot 2.0 handles things differently to 1.9*
Oct 18 12:18:34 <blaster8> which is why you're running into these issues, but NSLU2 isn't
Oct 18 12:18:50 <blaster8> anyway, can you test that quick hack as I've got to rush off :)
Oct 18 12:19:33 <[g2]> blaster8 I'm moving that 0xff patch up to 2.6.18 to test
Oct 18 12:19:52 <[g2]> that skips over all the null partition I think
Oct 18 12:20:08 <[g2]> blaster8 cheers and thx for all the help / ideas
Oct 18 12:20:09 <blaster8> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=84e699e6ec5b431289474f78f8df9dfcc2737085
Oct 18 12:20:18 <blaster8> that's the patch it was introduced in
Oct 18 12:20:35 <blaster8> very little has changed in redboot.c: http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;h=b020bb7d3b3a8e3568a16eaf98c033bb9ee474eb;f=drivers/mtd/redboot.c
Oct 18 12:27:09 <[g2]> blaster8 that's it
Oct 18 12:27:33 <likewise> swap32s()?   http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=77a3313551afd53c90012e5a87f7f2b2195fc67e
Oct 18 12:27:47 <[g2]> http://pastebin.ca/208129
Oct 18 12:28:02 <[g2]> the == 0xff and the break
Oct 18 12:29:26 <[g2]> oh it's much happier
Oct 18 12:30:05 <likewise> [g2]: what exactly did you do now? take 2.6.18 and the 0xff patch?
Oct 18 12:36:17 <[g2]> likewise yeah
Oct 18 12:37:11 <[g2]> likewise http://pastebin.ca/208139
Oct 18 12:38:08 <[g2]> bbl -- out for a bagel
Oct 18 13:25:24 <[g2]> re
Oct 18 13:28:24 <likewise> [g2]: wb
Oct 18 13:29:14 <[g2]> thx
Oct 18 13:29:38 * [g2] tries mounting jffs2 partition now that the partition numbers are sane
Oct 18 13:31:34 <[g2]> hmm... still a little more testing to do
Oct 18 13:33:22 <[g2]> then again maybe not
Oct 18 13:37:57 <[g2]> Gone!
Oct 18 13:38:44 <[g2]> another bug bites the dust
Oct 18 13:41:45 <likewise> [g2]: generic bug or LOFT specific? Of course we would like to hear :-)
Oct 18 13:41:57 <likewise> [g2]: You are now 2.6.18 complete?
Oct 18 13:42:44 <likewise> Hmmn, programming a Stratix with a C copy to GPIO is 2 MHz instead of max. 100 MHz, takes 3 secs... Maybe I should revert to assembler <mumble>
Oct 18 13:44:40 * [g2] just one item on my current punchlist
Oct 18 13:45:16 <[g2]> the new NPE driver randomizes MACs and doesn't pull from the EEPROM
Oct 18 13:45:54 <[g2]> dwery refreshed the eeprom notifier patch and it just needs to be copied to the platform mac data
Oct 18 13:46:17 <[g2]> and verified that the new driver uses that mac
Oct 18 13:46:27 <[g2]> s/that mac/those macs/
Oct 18 13:46:27 <jbot> [g2] meant: and verified that the new driver uses those macs
Oct 18 13:46:44 <[g2]> likewise where are you pulling your MACs from ?
Oct 18 13:52:22 <likewise> [g2]: EEPROM
Oct 18 13:52:34 <likewise> [g2]: but not yet in Linux...
Oct 18 13:53:00 <[g2]> likewise 256 into it ?
Oct 18 13:53:06 <likewise> [g2]: right on.
Oct 18 13:53:14 <[g2]> I've got your patches :)
Oct 18 13:53:21 <likewise> [g2]: huh?
Oct 18 13:53:36 <likewise> [g2]: The 2.4 ones? :-)
Oct 18 13:53:44 <[g2]> 2.6 ones
Oct 18 13:53:59 <[g2]> the ones to make the eeprom work right
Oct 18 13:54:16 <[g2]> make pulling the macs from eeprom work right
Oct 18 13:54:23 <likewise> *my* *linux* patches?
Oct 18 13:54:46 <[g2]> no not "your" linux patches
Oct 18 13:55:00 <likewise> [g2]: ah, I was already wondering.
Oct 18 13:55:10 <[g2]> you're on .17 though right ?
Oct 18 13:55:14 <likewise> yes
Oct 18 13:55:55 <[g2]> ok so the eeprom patch I'm working on for .18 will work for you also
Oct 18 13:56:07 <[g2]> assuming you were on .18
Oct 18 13:56:32 <likewise> [g2]: I hope to be soon
Oct 18 13:56:49 <[g2]> hey are you guys selling hw yet ?
Oct 18 13:56:50 <likewise> [g2]: you're building from openembedded.org ?
Oct 18 13:57:12 <[g2]> nslu2-linux kernel repo + some extra patches
Oct 18 13:57:22 <likewise> [g2]: no xscale h/w yet, but we have two newer designs based on the ixp425 in the works
Oct 18 13:57:49 <[g2]> need alpha testers ? :)
Oct 18 13:57:50 <likewise> [g2]: the first products has been lowered priority, but its prototype is no used as a reference for the newer designs.
Oct 18 13:58:22 <[g2]> do you use a 14-pin or 20-pin JTAG ?
Oct 18 13:58:56 <likewise> [g2]: micromatch connector, but with a 20-pin converter.
Oct 18 13:59:15 <[g2]> mictor ?
Oct 18 13:59:17 <likewise> [g2]: The card pulls power from a custom pinned cPCI slot.
Oct 18 13:59:21 <likewise> dunno
Oct 18 13:59:27 <[g2]> ah cPCI
Oct 18 13:59:46 <likewise> [g2]: They hot swap in to a 19" rack.
Oct 18 13:59:56 <[g2]> cool
Oct 18 14:00:49 <likewise> btw, any chance to meet at FOSDEM or alike? (Never been there myself, will be in 2007)
Oct 18 14:01:20 <[g2]> hmmm when is it ?
Oct 18 14:02:00 <likewise> [g2]: end of feb
Oct 18 14:02:05 <likewise> [g2]: brussels
Oct 18 14:02:55 <[g2]> cool
Oct 18 14:02:58 <likewise> [g2]: I will at least attend the embedded room presentations and hope to meet the guys that make the tooling work (OE etc)
Oct 18 14:03:26 <likewise> [g2]: I am not sure how many nslu2 fooks will be there.
Oct 18 14:03:48 <[g2]> well I'd guess lennert, koen and others
Oct 18 14:23:45 <barnseenio> [g2]: 
Oct 18 14:24:03 <barnseenio> i appear to have managed to get libtorrent to configure on the slug itself
Oct 18 14:30:35 <eno> barnseenio: if you look at optware/sources/libtorrent/ to x-build libtorrent there needs to be just 1 patch to configure
Oct 18 14:30:41 <likewise> [g2]: can your ixp4xx design reset the board (most notably the flash) upon a Linux panic or reboot?
Oct 18 14:31:13 <barnseenio> where is /optware/sources/libtorrent
Oct 18 14:31:25 <barnseenio> and rakasha said this much ..
Oct 18 14:31:26 <barnseenio> 15:15 <@bb> 15:14 < rakshasa> you need to either compile on the arm box itself, or make sure configure doesn't try to compile any test programs
Oct 18 14:31:29 <barnseenio> 15:15 <@bb> 15:14 < rakshasa> for f.ex mincore and align
Oct 18 14:32:36 <barnseenio> k i see her e?.. exeterdeb:/home/nslu2/slug/optware/sources
Oct 18 14:33:02 <eno> barnseenio: yes
Oct 18 14:33:27 <barnseenio> excuse my ignorance, im not really even sure what this optware dir is, is it all packages built into slugos?
Oct 18 14:33:33 <eno> also the native compilation is also a good start
Oct 18 14:34:12 <eno> optware packages are for unslung f/w
Oct 18 14:34:14 <barnseenio> oh lol, i had that error that the configure.patch seems to patch out
Oct 18 14:34:58 <eno> slugos use a different x-compilation environment
Oct 18 14:35:23 <eno> and the x-compilation recipes are under openembedded/packages/
Oct 18 14:35:56 <barnseenio> oo, that sounds more useful, as my problem was running ./configure for libtorrent and making it, it just seemed to ignore my request for it to use the arm-linux-gcc 
Oct 18 14:37:06 <eno> i'm not sure there's libtorrent package for slugos
Oct 18 14:37:52 <barnseenio> im running slugos/le  - debianslug
Oct 18 14:38:38 <eno> for cross compilation, i see basically 3 setup: 1. openembedded bitbake; 2. optware; 3. scratchbox
Oct 18 14:39:36 <eno> in your debianslug/le case, easiest might be native compilation, and (optionally) have distcc to do the heavy lifting
Oct 18 14:39:56 <joshin> I know that works great for GentooSlug.  :)
Oct 18 14:41:17 <eno> if you decide to go with x-compilation, even though you're not using 1 or 2, their recipes and patches are good for reference
Oct 18 14:43:06 <barnseenio> mm distcc i read that page you posted to the wiki on that
Oct 18 14:43:44 <barnseenio> well, if this make finishes on the slug itself, i'll probly give up on my foray into x-compiling
Oct 18 14:47:25 <barnseenio> its been a painful experience from which ive nnot really learned many useful lessons!
Oct 18 15:06:39 <joshin> [g2], You around?
Oct 18 15:06:52 <[g2]> joshin yup
Oct 18 15:07:16 <joshin> My build from last night (12 hours ago) did not pick up the randomize MAC address patch.
Oct 18 15:07:52 <joshin> Is that on the SVN/MTN repositories that the master makefile grabs?
Oct 18 15:08:10 <[g2]> joshin I don't know if the changes are rolled up into OE or not
Oct 18 15:08:16 <[g2]> they are usually pretty in sync
Oct 18 15:08:36 <[g2]> i've been working out of the nslu2-linux kernel repo
Oct 18 15:09:18 <joshin> Ok.  Will try again later or I get impatient enough will try that repo.  :)  Thanks!
Oct 18 15:11:08 <[g2]> np
Oct 18 15:23:03 <blaster8_> ping: dwery
Oct 18 17:50:42 <barnseenio> lol, i see why you guys use cross compilers, libtorrent has been compiling on my slug for nearly two hours ;-)
Oct 18 17:51:01 <[g2]> barnseenio heh :)
Oct 18 18:27:14 <barnseenio> [g2]:  still alive?
Oct 18 18:27:39 <[g2]> barnseenio fortunately :)
Oct 18 18:27:51 <barnseenio> heh, a question ...
Oct 18 18:28:00 <[g2]> barnseenio NO
Oct 18 18:28:05 <[g2]> a answer :)
Oct 18 18:28:19 <[g2]> hmmm MAYBE
Oct 18 18:28:42 <[g2]> barnseenio just kidding around, what' the Q ?
Oct 18 18:28:44 <barnseenio> what would be involved in creating a partition on my 500gb disk which is fat, and then copying a bunch of my movies/files etc into the fat partition. and still accessing that partition from debian/samba/other stuff
Oct 18 18:28:58 <barnseenio> at present my entire disk is partitioned as ext3
Oct 18 18:29:32 <[g2]> fat doesn't support symlinks
Oct 18 18:30:02 <[g2]> but other than that and large file support (> 2G files) a fs is an fs
Oct 18 18:30:18 <[g2]> I woudn't copy to FAT
Oct 18 18:30:29 <[g2]> I'd just samba mount the ext3
Oct 18 18:31:38 <[g2]> but really, you pobably just want to unplug the disk and do the copying as the network performance will be miserable compared to direct connect
Oct 18 21:22:56 <barnseenio> anyone about?
Oct 18 21:23:00 <blaster8> yes
Oct 18 21:23:27 <barnseenio> i want to 'set a make going' and disconect my terminal
Oct 18 21:23:33 <barnseenio> when i run make & 
Oct 18 21:23:42 <eno> screen is your friend
Oct 18 21:23:43 <barnseenio> it still drops when i kill the ssh
Oct 18 21:23:50 <barnseenio> oh, has to be screen'd
Oct 18 21:24:04 <eno> or nohup
Oct 18 21:24:09 <barnseenio> i'll screen
Oct 18 21:24:09 <barnseenio> ta
Oct 18 21:24:12 <eno> but screen is just easier
Oct 18 21:24:41 <eno> detach the screen if you want to leave
Oct 18 21:33:52 <likewise> eno: CTRL-A D to detach, right??
Oct 18 21:37:37 <eno> yes
Oct 18 21:38:04 <eno> search online, there're some nice .screenrc you can use
Oct 18 21:38:35 <eno> showing you window# and window title, date, sort of things
Oct 18 23:04:18 <likewise> good nite all
Oct 18 23:28:06 <CIA-8> 03g2-tbillman * r492 10kernel/trunk/patches/2.6.18/ (10-br.patch series): Recent bridging patch. Lennert has already submitted upstream.
Oct 18 23:31:08 <CIA-8> 03g2-tbillman * r493 10kernel/trunk/patches/2.6.18/ (3 files): 
Oct 18 23:31:08 <CIA-8> Restore RedBoot partition patch accidentally deleted from 2.6.16. Clean up type warning in
Oct 18 23:31:08 <CIA-8> 11-mtdpart-redboot-config-byteswap.patch. 12-redboot-partition.patch needs to go upstream also.
Oct 18 23:36:57 <CIA-8> 03g2-tbillman * r494 10kernel/trunk/patches/2.6.18/ (4 files): 
Oct 18 23:36:57 <CIA-8> Add basic Loft support back to the kernel. Note: since the Loft boot directly to hda1 or sda1 the ext2/3/usb/scsci
Oct 18 23:36:57 <CIA-8> modules are almost always included in the kernel. Added separate loft_defconfig. 96-loft-ide-le.patch needs support
Oct 18 23:36:57 <CIA-8> for BE.
**** ENDING LOGGING AT Thu Oct 19 02:59:57 2006