**** BEGIN LOGGING AT Wed Mar 08 10:59:56 2006
Mar 08 11:20:07 <Neuer_User> :-(
Mar 08 11:32:39 <Neuer_User> so, just as a test, I reused my old build that gave me the qemu-errors yesterday ( mv slug slug-new && mv slug-old slug )
Mar 08 11:33:03 <Neuer_User> making the debianslug-image gave the same error as yesterday
Mar 08 11:33:17 <Neuer_User> make update downloaded 6 revisions
Mar 08 11:33:42 <Neuer_User> make debianslug-image then gave the same ixp error as with the from-scratch-try
Mar 08 11:34:17 <Neuer_User> So it seems that yesterday there was an error in the sources that stopped with the qemu-native dependency
Mar 08 11:34:38 <Neuer_User> today, on the other hand, there seems to be an error with the ixp modules
Mar 08 11:34:53 <Neuer_User> maybe I should wait and try again tomorrow...
Mar 08 12:00:18 <Neuer_User> Last thing: I redownloaded the IXP code from intel and verified it to be identical with the one I downloaded at the beginning of the year...
Mar 08 12:00:39 <Neuer_User> guess, I'll just try again tomorrow or next week... :-(
Mar 08 14:17:56 <kolla> I wonder... did anyone try hooking a plextor convertX to a slug? :)
Mar 08 14:18:08 <kolla> it's a hardware mpeg/divx encoder
Mar 08 14:20:44 <NAiL> does it have a linux driver? :)
Mar 08 14:21:08 <Neuer_User> as far as I know there is a linux driver available
Mar 08 14:23:52 <kolla> NAiL: yes
Mar 08 14:24:04 <kolla> NAiL: http://hardware.newsforge.com/article.pl?sid=05/07/01/0353218&tid=125&tid=24
Mar 08 14:24:52 <kolla> heh, it has integrated tuner as well
Mar 08 14:24:56 <kolla> cute
Mar 08 14:26:34 <NAiL> well, noone has done it so far, afaik
Mar 08 14:26:45 <NAiL> feel free to try ;)
Mar 08 14:26:50 <NAiL> how much does it cost?
Mar 08 14:27:52 <kolla> about $200 
Mar 08 14:27:56 <kolla> havnet found any norwegian dealers yet
Mar 08 14:28:16 <kolla> haven't
Mar 08 14:31:36 <kolla> there... ~ NOK600 for the simpler version without tuner and ~1250 for the one with tuner
Mar 08 14:32:08 <kolla> http://prisguide.hardware.no/product.php?product_id=28687 and http://prisguide.hardware.no/product.php?product_id=24005
Mar 08 14:41:58 <NAiL> might be worth taking a look at ;)
Mar 08 14:42:50 <kolla> mm
Mar 08 14:42:52 <kolla> NAiL: btw.. http://www.dagsavisen.no/debatt/article1986109.ece
Mar 08 14:43:04 <kolla> quite funny
Mar 08 14:43:40 <kolla> difficult this "for" and "mot" stuff :)
Mar 08 14:50:43 <caplink811_log> version raises up to since my last build
Mar 08 14:51:05 <caplink811_log> oops, wrong window
Mar 08 14:51:43 <Neuer_User> I just did a make update again -> got 3 new revs -> now compile error with "file-native-4.16-r0: task do_compile: failed"
Mar 08 16:30:28 <pepijn> can someone explain the difference between development @ openembedded.org vs. svn.berlios.de ?
Mar 08 16:30:44 <pepijn> what happens where? what is the relationship between the two?
Mar 08 17:17:58 <NAiL> The work on svn.berlios.de is fixes to the releases and their feeds
Mar 08 17:18:10 <NAiL> the work on OE is the current development
Mar 08 17:22:49 <pepijn> and the trunk on svn ?
Mar 08 17:26:15 <NAiL> hmm, dunno
Mar 08 17:26:28 <pepijn> hehe, dead probably ;)
Mar 08 17:26:51 <NAiL> It's not anything that I touch
Mar 08 17:26:59 <pepijn> but you pull (acceptable?) changes from OE and merge them into the SVN repository ?
Mar 08 17:27:08 <NAiL> yes
Mar 08 17:27:20 <NAiL> That's more or less done only by me
Mar 08 17:27:39 <pepijn> yes, i figured so much from the logs and discussions in here
Mar 08 17:28:11 <pepijn> and that also means that OE is a fast moving target, while svn is a controlled environment, right?
Mar 08 17:28:19 <NAiL> yes
Mar 08 17:28:31 <NAiL> after a release, there will be no changes that affects the root fs
Mar 08 17:28:41 <NAiL> (eg. kernel fixes)
Mar 08 17:29:13 <NAiL> So there's just the odd fix for problems that are reported on slugbug mainly
Mar 08 17:29:17 <NAiL> or are discussed here
Mar 08 17:29:38 <pepijn> what about the changes in the Makefile
Mar 08 17:29:58 <pepijn> svn uses the (more appropriate) lag bag etc targets
Mar 08 17:30:10 <pepijn> while OE seems to use the (older?) targets
Mar 08 17:30:24 <NAiL> well... that depends
Mar 08 17:30:46 <NAiL> slugos-* is the base for the various openslug/ucslugc/debianslug distros
Mar 08 17:32:53 <pepijn> still, this double development is sort of confusing
Mar 08 17:33:01 <pepijn> OE is *everything*
Mar 08 17:33:07 <pepijn> svn is kernel+rootfs
Mar 08 17:33:15 <pepijn> for 'stable' releases
Mar 08 17:33:22 <NAiL> no, svn is everything
Mar 08 17:33:26 <NAiL> it's a snapshot of OE
Mar 08 17:33:43 <pepijn> in my case (Debian LE) the packages come from somehwere else (Debian)
Mar 08 17:33:57 <pepijn> but for the others, the OE is used for ipkg's ?
Mar 08 17:34:22 <NAiL> for stable releases, the ipkgs are built from svn, for unstable the ipkgs are built from OE
Mar 08 17:34:46 <pepijn> except for the Debian variants
Mar 08 17:35:05 <NAiL> yes
Mar 08 17:35:18 <pepijn> i am really just interested in the kernel and modules belonging to it
Mar 08 17:35:32 <NAiL> debian-le will eventually become a debian-installer image with a small rootfs in flash, just to install debian to the hdd
Mar 08 17:35:33 <pepijn> and the part that boots (pivots) into the USB disk
Mar 08 17:36:14 <NAiL> yeah, that's the small rootfs
Mar 08 17:36:15 <pepijn> nice thing about the flash rootfs is that it is quite useful for troubleshooting/recovery
Mar 08 17:36:19 <NAiL> yeah
Mar 08 17:37:00 <pepijn> but, ref. ipkgs, those you also pull out of OE and merge into svn ?
Mar 08 17:37:27 <NAiL> yes
Mar 08 17:37:39 <pepijn> that is quite a job, then
Mar 08 17:37:58 <pepijn> if you were just maintaining the rootfs+kernel, i could understand
Mar 08 17:38:10 <pepijn> but every package as well makes it a huge project
Mar 08 17:38:40 <NAiL> well, I watch the commit mailinglist, so I see if there are relevant fixes that I would like to backport
Mar 08 17:39:02 <pepijn> commit mailinglist?
Mar 08 17:39:08 <NAiL> yes, oe-commit
Mar 08 17:39:21 <pepijn> but that is *everything* oe related ?
Mar 08 17:39:26 <NAiL> yup
Mar 08 17:39:27 <pepijn> i mean, all projects in OE?
Mar 08 17:39:54 <NAiL> yes
Mar 08 17:40:00 <NAiL> so there's a lot of stuff I just ignore
Mar 08 17:40:08 <pepijn> yes, i hope you do ;)
Mar 08 17:40:30 <NAiL> eg. koen's recent avalance of ep93xx-related stuf
Mar 08 17:41:51 <pepijn> still, quite a challenge
Mar 08 17:42:53 <pepijn> ref. debian-installer: what is the status? who are the contacts?
Mar 08 17:43:22 <NAiL> as far as I know, rwhitby, dwery-away and tbm are the ones working on it
Mar 08 17:43:30 <NAiL> I haven't watched that very closely
Mar 08 17:44:10 * mwester wonders if maybe it would be just easier to release Unslung from MAiL's OE svn tree instead of the Unslung svn tree...
Mar 08 17:44:14 <NAiL> The nslu2 kernel patches need to go mainstream first afaik
Mar 08 17:44:38 <pepijn> yes, i read about that
Mar 08 17:44:45 <NAiL> mwester: hmm... might not be a too bad idea
Mar 08 17:44:57 <pepijn> my point exactly ;)
Mar 08 17:45:00 <NAiL> I'm no unslung dev though
Mar 08 17:45:40 <pepijn> or, does Unslung have yet another point of maintenance?
Mar 08 17:46:12 <NAiL> Unslung uses OE packages afaik. So it's currently being built out of HEAD
Mar 08 17:46:30 <pepijn> i do understand the reasons (or 'how it got to be') behind all those different repositories
Mar 08 17:46:41 <pepijn> but it does not make for easy development paths
Mar 08 17:46:52 <NAiL> no, but it's the best solution that I can see
Mar 08 17:47:07 <NAiL> since maintaining a separate head in OE would be a real pain
Mar 08 17:47:09 <tbm> pepijn: the following page shows instructions and the status: http://www.cyrius.com/debian/nslu2/
Mar 08 17:47:22 <tbm> pepijn: right now the installer is broken but there's a fix already, so it'll work again soon
Mar 08 17:47:28 <pepijn> hehe, been there, read that
Mar 08 17:48:00 <tbm> right.  so that's the status.  it basically works but lacks in: some kernel features (LEDS, RTC), automatically writing the kernel to flas
Mar 08 17:48:01 <pepijn> yay! the slug-firmware.net now actually shows the debian-installer thingy
Mar 08 17:48:05 <tbm> flash
Mar 08 17:48:22 <pepijn> i see the source is available there
Mar 08 17:48:32 <pepijn> which repository is used?
Mar 08 17:48:35 <pepijn> branch?
Mar 08 17:48:36 <pepijn> etc
Mar 08 17:48:57 <pepijn> and where is development being discussed? debian-installer mailinglist?
Mar 08 17:49:15 <tbm> svn+ssh://svn.d-i.alioth.debian.org/svn/d-i/trunk
Mar 08 17:49:19 <tbm> debian-boot@lists.debian.org
Mar 08 17:49:29 <pepijn> thnx
Mar 08 17:50:52 <tbm> but note that it's broken right now.  should work tomorrow or the day after
Mar 08 17:51:11 <pepijn> yes, i noted
Mar 08 17:51:45 <pepijn> (and, on a sidenote, yet another repository... )
Mar 08 17:52:33 <pepijn> well, i guess d-i and rootfs for NSLU2 can be seen as seperate, but related projects
Mar 08 18:01:41 <pepijn> tbm: what about the 'rescue' function of the flash rootfs?
Mar 08 18:02:19 <tbm> pepijn: not yet
Mar 08 18:03:39 <pepijn> will that be the same rootfs, or will the rootfs be replaced after the installation?
Mar 08 18:03:57 <tbm> not sure yet
Mar 08 18:05:57 <pepijn> that was a RTFM ;)
Mar 08 18:10:56 <NAiL> ah, finally
Mar 08 18:10:59 <pepijn> any sign of an opensource ethernet replacement?
Mar 08 18:11:03 <NAiL> nope
Mar 08 18:11:20 <pepijn> so that will be the major issue for the debian versions, then
Mar 08 18:14:20 <tbm> pepijn: a RTFM?  no, I'm just not sure myself yet what the best way is to implement it.
Mar 08 18:14:49 <pepijn> my q. about the rescue feature, it says so on the web page
Mar 08 18:15:01 <tbm> yeah, true
Mar 08 18:15:58 <pepijn> i see basically two options: 1) make a d-i that has an alternative path (drop to shell is there already, isn't it)
Mar 08 18:16:18 <pepijn> or 2) replace the rootfs with the rootfs from NAiL
Mar 08 18:16:39 <pepijn> both options do have the closed source ixp problem, though
Mar 08 18:17:39 <NAiL> pepijn: Don't attribute the rootfs to me, there's a lot of people behind that ;)
Mar 08 18:18:15 <pepijn> no, no... just a figure of speech
Mar 08 18:18:20 <pepijn> ;)
Mar 08 18:18:28 <pepijn> teh SVN one then?
Mar 08 18:18:31 <pepijn> or how to call it
Mar 08 18:18:50 <NAiL> the released slugos rootfs ;)
Mar 08 18:18:58 <NAiL> in this case, slugos-lag
Mar 08 18:19:10 <pepijn> officially released beta slugos-lag ?
Mar 08 18:19:23 <pepijn> haha
Mar 08 18:19:28 <NAiL> hehe
Mar 08 18:20:44 <pepijn> but i do realise it is not just you responsible for it (although from what you told earlier you are performing quite a keyrole in the release process)
Mar 08 18:20:54 <pepijn> and all those q's are:
Mar 08 18:20:58 <pepijn> 1) because i am curious
Mar 08 18:21:17 <pepijn> 2) because i do have capabilities (and hopefully resources) to do some sort of testing
Mar 08 18:21:40 <pepijn> just trying to figure out what is in my (and the communities) best interest ;)
Mar 08 18:26:49 <NAiL> I'm just waiting for 2.6.16 so I can start testing slugos-* myself ;)
Mar 08 18:28:42 <pepijn> currently thinking that that is the most efficient thing to do... take the svn beta-3.6 branch (*after* insertion of the 2.6.16 bits) and test it as the Debian LE rescue root
Mar 08 18:34:20 <NAiL> yeah
Mar 08 18:34:34 <NAiL> I'm waiting for that myself. That, and the OpenSlug rootfs
Mar 08 18:53:04 <NAiL> hmm
Mar 08 18:53:06 <NAiL> this is strange
Mar 08 18:53:29 <NAiL> upslug2 appears to not communicate with redboot
Mar 08 18:57:31 <NAiL> oh well
Mar 08 18:57:35 <NAiL> worked with telnet
Mar 08 19:15:40 <NAiL> *sigh*
Mar 08 19:15:47 <NAiL> upgrading busybox sucks
Mar 08 19:31:44 <dwery-away> NAiL: I'm not working on d-i, sorry :)
Mar 08 19:35:19 <NAiL> well, you're working on getting the kernel-patches pushed, aren't you? ;)
Mar 08 19:37:36 * NAiL debootstraps
Mar 08 19:55:20 <dwery-away> NAiL: yep
Mar 08 20:39:36 <NAiL> aaaaaah
Mar 08 20:39:45 <NAiL> openssh key generation takes *forever*
Mar 08 20:47:08 <mwester> NAiL: would "ln /dev/random /dev/zero" help?  ;)
Mar 08 20:47:59 <NAiL> nah, it didn't run out of entropy
Mar 08 20:48:12 <NAiL> it just spent ages generating the key
Mar 08 20:48:27 <mwester> Ok... needs more CPU (or an FPU?)
Mar 08 20:48:36 <NAiL> an FPU would help
Mar 08 20:48:52 <NAiL> esp. since debian uses the kernel fp-emul
Mar 08 20:49:09 <mwester> Do any external (USB-attached) key generators exist?
Mar 08 20:51:14 <NAiL> I would assume that would require special drivers, but it should be possible
Mar 08 21:59:33 <marceln> mwester: I have a failure with a unslung 6.7 compile in file-native?
Mar 08 21:59:48 <marceln> Friday it worked.
Mar 08 22:10:35 <EvilDevil> hi. is there a mp3 player that can act as a shoutcast streaming client? 
Mar 08 22:18:28 <mwester> Somebody broke OE again?  Crud.  I've been checking every day or so, but not necessarily deleting the entire tmp/work tree and starting over.  I'll do that, and see what happens.  (I should have tagged the repository last Sunday when I *did* blow everything away and rebuild successfully!)
Mar 08 22:24:16 <marceln> They upgraded file from 4.13-r2 to 4.16-r1 and now the compiled "file" can't parse it's magic file
Mar 08 22:25:45 <EvilDevil> i'm getting the same error marceln
Mar 08 22:26:04 <mwester> Well, I don't know how to fix that.  So I guess we just wait until somebody in charge of the file package fixes it?
Mar 08 22:27:18 <EvilDevil> i think i read that you can define which version of a package should be used. somewhere around the openembedded/conf/distro i think (but i'm not sure)
Mar 08 22:28:22 <EvilDevil> #PREFERRED_VERSION_gcc-cross-initial ?= "3.4.4"
Mar 08 22:28:30 <EvilDevil> something like that?
Mar 08 22:30:08 <mwester> Yeah, but is it the right solution -- to "nail down" unslung to an old version of "file" because somebody hasn't fixed the new one?   I don't enough about Monotone, but ideally I'd like to go back to the revision from Sunday when it worked, and then "stretch" that revision forward to cover the README and NOTES changes I made yesterday, and the conf change to denote Unslung6.7-Beta that will...
Mar 08 22:30:10 <mwester> ...happen shortly, then tag THAT combination as what makes the release.  And let the monotone head do what it does - which is pretty much be "unstable"...
Mar 08 22:33:18 <pepijn> i have the same problem with file when building debianslug
Mar 08 22:33:48 <pepijn> guess for now it is either (a) wait til it is fixed, or (b) pin down the version of file to the previous one
Mar 08 22:34:13 <EvilDevil> i understand your point of view. but i just wanted to build an openslug-image with audio player capabilities 
Mar 08 22:34:16 <mwester> Well, then maybe (as ugly as it seems to me) if its breaking all the projects, the solution is (b) until the originator of the change fixes it.
Mar 08 22:34:28 <pepijn> yep
Mar 08 22:34:57 <pepijn> where would one do that?
Mar 08 22:35:28 <mwester> There's the problem - don't know.
Mar 08 22:35:43 <EvilDevil> NOTE: preferred version 4.13-r2 of file-native not available
Mar 08 22:35:48 * pepijn is grepping for the version number
Mar 08 22:36:10 <EvilDevil> edit ~/slug/openembedded/conf/distro/debianslug.conf and add
Mar 08 22:36:37 <EvilDevil> PREFERRED_VERSION_file-native ?= "4.13-r2"
Mar 08 22:36:52 <EvilDevil> (for debianslug)
Mar 08 22:37:32 <pepijn> looks plausible
Mar 08 22:37:33 <EvilDevil> well, it tries to build 4.13-r2, but there's no corresponding bb file in ~/slug/openembedded/packages/file/
Mar 08 22:37:51 <EvilDevil> NOTE: preferred version 4.13-r2 of file-native not available
Mar 08 22:37:51 <EvilDevil> NOTE: package file-native-4.16: started
Mar 08 22:41:55 <marceln> I just run "configure and make" over file and it works. So its really the build environment which breaks it.
Mar 08 22:42:05 <EvilDevil> seems like we have to wait 'til it's fixed
Mar 08 22:48:24 <marceln> The problem is that it can't parse the line ">>&0xf4 search/0x140 \x0\x40\x1\x0"
Mar 08 22:48:53 <marceln> It's the only line with a search statement.
Mar 08 22:48:57 <philpem> OK, that kernel update didn't help at all.
Mar 08 22:49:24 <philpem> Before the reload I got about 10-16 hours before the slug froze. Now I'm getting three or four if I'm lucky.
Mar 08 22:50:08 <pepijn> which kernel is that, philpem?
Mar 08 22:50:15 <pepijn> 2.6.15.1 or 2.6.16 ?
Mar 08 22:50:17 <philpem> Openslug /etc/init.d/sysklogd stop
Mar 08 22:50:18 <philpem> /etc/init.d/klogd stop
Mar 08 22:50:18 <philpem> modprobe netconsole netconsole=@/,514@10.255.255.255/
Mar 08 22:50:21 <philpem> 2.6.15.1
Mar 08 22:50:37 <philpem> Linux wolf.philpem.me.uk 2.6.15 #1 Tue Mar 7 09:59:02 GMT 2006 armv5teb GNU/Linux
Mar 08 22:50:55 <pepijn> as i said, i have been running stable with 2.6.16 since last week
Mar 08 22:51:05 <philpem> Bigendian or Littleendian?
Mar 08 22:51:18 <pepijn> after discussions yesterday and today i decided to stay on 2.6.16
Mar 08 22:51:35 <pepijn> that is, build from mastermakefile from OE and not (yet) from the svn branch on berlios
Mar 08 22:51:52 <pepijn> but currently building from OE fails
Mar 08 22:51:58 <pepijn> currently LE
Mar 08 22:52:06 <philpem> hmm
Mar 08 22:52:14 <pepijn> but i had freezes with both BE and LE Debian
Mar 08 22:52:14 <philpem> i'm beginning to wonder if this is a system load issue
Mar 08 22:52:28 <pepijn> for me it had nothing to do with system load
Mar 08 22:52:54 <philpem> I'm getting load averages of 1.08 idle without eciadsl, if i run BitTorrent that rockets up to 3.83 and the slug hangs within 4 hours
Mar 08 22:52:58 <philpem> nothing in syslog at all
Mar 08 22:53:01 <pepijn> but i am really unsure if our problems are related
Mar 08 22:53:15 <philpem> x86 is little-endian, right?
Mar 08 22:53:25 <pepijn> you are aware of the 1.0 offset for the load numbers ?
Mar 08 22:53:32 <philpem> 1.0 offset?
Mar 08 22:53:33 <pepijn> yes, x86 is LE
Mar 08 22:53:44 <pepijn> uptime shows a load of 1.0 when idle
Mar 08 22:54:02 <philpem> hmm. makes sense.
Mar 08 22:54:07 <philpem> i'm beginning to wonder if there's an endianness bug somewhere. a "heisenbug" if you will.
Mar 08 22:54:19 <pepijn> top show proper %-es, but the load numbers there are also off
Mar 08 22:54:39 <pepijn> that would make sense in a LE environment, IMHO
Mar 08 22:54:41 <philpem> or maybe something related to high usb load... that adsl modem chews a lot of bandwidth.
Mar 08 22:55:23 <philpem> but its running at 233. if i understand correctly, the cpu core will run at 233, but the system bus will stay at 33. that means there shouldn't be any issues with RAM timing or hardware.
Mar 08 22:55:28 <pepijn> can't you try hanging the modem off of another machine?
Mar 08 22:55:53 <philpem> could do.
Mar 08 22:56:17 <philpem> but the whole point of getting the nslu was to get the modem wired up to something that used less power than the x86 box i used to use.
Mar 08 22:56:45 <philpem> obviously its no good if it keeps hanging after a couple of hours though
Mar 08 22:56:46 <pepijn> yes, i understand that
Mar 08 22:56:59 <pepijn> but you do not know wether or not it is the modem
Mar 08 22:57:41 <pepijn> i would suggest trying to build openslug from OE
Mar 08 22:57:58 <philpem> OE=openembedded, i.e. the mastermakefile
Mar 08 22:57:59 <philpem> ?
Mar 08 22:58:00 <pepijn> but just before you came in we discussed a build problem
Mar 08 22:58:02 <pepijn> yes
Mar 08 22:58:18 <pepijn> file is not building, something was checked in that fails the build
Mar 08 22:58:58 <EvilDevil> i'm going to bed now, maybe it's fixed tomorrow ;-) n8 @ll
Mar 08 22:59:47 <pepijn> yeah, me too... talk later
Mar 08 23:17:27 <marceln> I sent a mail on the developer list about the file problems and hope it is solved to morrow.
Mar 09 00:11:40 <CIA-8> 03jp30 * 10unslung/Makefile: optware: demote cross w3m, promote memcached
Mar 09 01:04:29 <CIA-8> 03jp30 * 10unslung/make/mysql.mk: mysql: don't stage libtool archives
Mar 09 01:23:22 <CIA-8> 03azummo * 10kernel/2.6.16/ (4 files): Splitted nas100d patches
Mar 09 02:03:52 <CIA-8> 03jp30 * 10unslung/Makefile: optware: promote rubygems, lighttpd, various python modules
Mar 09 02:04:03 <eno-away> jp30, ping?
Mar 09 02:04:11 <jp30-work> hi, eno
Mar 09 02:04:44 <eno-away> hi josh, i just removed host libgc from my build machine, and made some further change to w3m.mk
Mar 09 02:05:00 <jp30-work> ok, have you got it to build?
Mar 09 02:05:01 <eno-away> can you check again on that?
Mar 09 02:05:05 <jp30-work> will do...
Mar 09 02:05:12 <eno-away> i'll check in soon
Mar 09 02:05:40 <eno-away> if it passes, do we need to bump the IPK_VERSION?
Mar 09 02:06:12 <jp30-work> i'll keep an eye out for your commit.  bumping the ipk version would be a good idea
Mar 09 02:06:28 <eno-away> i did build it successfully
Mar 09 02:07:17 <CIA-8> 03bzhou * 10unslung/make/w3m.mk: determined to get w3m to x-compile, bumped IPK_VERSION again
Mar 09 02:09:25 <jp30-work> eno, it's not working for me...
Mar 09 02:09:27 <jp30-work> checking for GC_init in -lgc... no
Mar 09 02:09:27 <jp30-work> checking GC library location... /usr /usr/local /home/jp30
Mar 09 02:09:27 <jp30-work> checking /usr... checking for GC_init in -lgc... no
Mar 09 02:09:27 <jp30-work> checking /usr/local... checking for GC_init in -lgc... no
Mar 09 02:09:27 <jp30-work> checking /home/jp30... checking for GC_init in -lgc... no
Mar 09 02:09:27 <jp30-work> configure: error: libgc not found
Mar 09 02:10:14 <jp30-work> oh, and there seems to be trouble with openssl as well, perhaps you are depending on host openssl headers?
Mar 09 02:31:40 <eno-away> ok, i'll need to look at the problems
Mar 09 02:32:34 <eno-away> i added a couple of echo lines, could you tell me the last echo output?
Mar 09 02:33:13 <eno-away> something like =================
Mar 09 02:37:37 <eno-away> checking GC library exists... /home/bzhou/slug/optware/nslu2/builds/w3m/libgc-hostbuild/opt
Mar 09 02:37:37 <eno-away> checking gc.h usability... no
Mar 09 02:37:37 <eno-away> checking gc.h presence... no
Mar 09 02:37:37 <eno-away> checking for gc.h... no 
Mar 09 02:37:37 <eno-away> checking GC header location... /home/bzhou/slug/optware/nslu2/builds/w3m/libgc-hostbuild/opt
Mar 09 02:37:37 <eno-away> checking /home/bzhou/slug/optware/nslu2/builds/w3m/libgc-hostbuild/opt/include... checking gc.h usability... yes
Mar 09 02:37:41 <eno-away> checking gc.h presence... yes
Mar 09 02:37:43 <eno-away> checking for gc.h... yes 
Mar 09 02:37:44 <eno-away> checking for GC_init in -lgc... no
Mar 09 02:37:47 <eno-away> checking GC library location... /home/bzhou/slug/optware/nslu2/builds/w3m/libgc-hostbuild/opt
Mar 09 02:37:48 <eno-away> checking /home/bzhou/slug/optware/nslu2/builds/w3m/libgc-hostbuild/opt... checking for GC_init in -lgc... yes
Mar 09 02:38:30 <jp30-work> eno, i'll email you some build logs to your sourceforge address
Mar 09 02:41:57 <eno-away> alright, thx. Yes i can be more specific in the last w3m cross configuration, --with-gc and --with-ssl
Mar 09 02:43:59 <jp30-work> those logs are on their way now.
Mar 09 03:44:54 <mwester> rwhitby: ping
Mar 09 04:20:29 <CIA-8> 03bzhou * 10unslung/make/w3m.mk: configure host w3m --without-ssl, be explicit when configuring cross w3m on ssl and gc locations
Mar 09 04:41:45 <CIA-8> 03bzhou * 10unslung/make/w3m.mk: --disable-image for host w3m configure, all we need from host w3m configure is just the mktable binary
Mar 09 09:48:08 <philpem> well, i think i've found an entry on slugbug that matches the problems i'm having... http://slugbug.nslu2-linux.org/bug.php?op=show&bugid=330&pos=4
Mar 09 09:48:40 <philpem> except in my case removing the clock-lock resistor didn't help much at all...
**** ENDING LOGGING AT Thu Mar 09 10:59:57 2006