From tp at fonz.de Mon May 14 20:26:20 2007 From: tp at fonz.de (Tobias Poschwatta) Date: Mon, 14 May 2007 22:26:20 +0200 Subject: [armedslack] glibc and --enable-kernel Message-ID: <20070514202620.GY1708@kiwi> Hi there, I was about to try ARMedslack on my D-Link DNS-323. It's got an ARM926EJ-S (armv5l), 64MB RAM and two SATA ports: http://www.dlink.com/products/?pid=509 Typically, this kind of embedded device (especially those from D-Link, it seems) comes with really buggy firmware and very limited functionality (e.g. the DNS323 offers an old samba 2.2.8, but no NFS). So people start to "customize", which usually means they install Debian. Since I'm using Slackware wherever possible for quite a few years now, I prefer ARMedslack over Debian/ARM. Tried and failed. Here's why: FATAL: kernel too old which I found out is most likeley the result of this line in glibc.SlackBuild: --enable-kernel=2.6.20 \ Problem is that most DNS-323 components are not supported by vanilla kernels (yet). D-Link ships 2.6.12.6-arm1, and porting the drivers to newer kernels is probably difficult and very time-consuming. What's the reason for the 2.6.20 requirement? Tobias From m-lists at biscuit.org.uk Mon May 14 20:42:04 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 14 May 2007 21:42:04 +0100 (BST) Subject: [armedslack] glibc and --enable-kernel In-Reply-To: <20070514202620.GY1708@kiwi> References: <20070514202620.GY1708@kiwi> Message-ID: Hi Tobias > What's the reason for the 2.6.20 requirement? I chose 2.6.20 because the version of coreutils in -current didn't work with anything less than or equal to Linux 2.6.19. There was something (a syscall?) that wasn't implemented in ARM Linux until 2.6.20. You could install ARMedslack-11.0 since that works with 2.4 & 2.6 Kernels. From mozes at slackware.com Tue May 15 10:19:14 2007 From: mozes at slackware.com (Stuart Winter) Date: Tue, 15 May 2007 03:19:14 -0700 (PDT) Subject: [armedslack] Re: crossbuilding and armedslack In-Reply-To: References: Message-ID: Hi Bryce I've CC'd the armedslack mailing list - I like to share information with more than 1 person where I can. You can join the list too - the info's on the web site. > Thanks for ARMedslack. Here's how I'm using it at the moment: Cool - I like to hear from people who are using it :-) > I wanted to see if you had any pointers for cross-compiling. Do you use > the scratchbox toolchain? No I have not used scratchbox for many years - I only used it to initially get the project off the ground and build the initial packages. I stopped using it for a number of reasons - mostly because at the time I could not choose my own compiler, and the SB compiler was compiling (by default) for an architecture higher than armv3, and I also needed to change versions of gcc to keep up with Slackware. What I do now is build on a QEMU host using bridged networking and use distcc to build on a number of x86 hosts. This is my script to make a cross toolchain on an x86 host. It just makes what you need to be able to use distcc -- so it's not a full toolchain: ftp://ftp.armedslack.org/armedslack/armedslack-current/source/x-toolchain/ If you put all of your armedslack-current tree onto your x86 host you should be able to run the script in there. I have some other bits I then use -- but they're a bit embarassing but it all works :-) I'll send you the script I use to wrap the arm/build scripts you find in the armedslack tree if you want. Hmm actually I might put all this stuff into the armedslack-devel directory on the ftp site, since I'm getting a few questions about how I build stuff. > There are a few packages I will be using that I'd be glad to help > maintain: MySQL, freetype, DirectFB (though I don't think DirectFB is in > slackware yet . . .). Let me know if this would be helpful. I tend to just diff Pat's scripts against mine and merge in changes. I always do the building of packages, and would love to see people testing the packages & giving feedback with build script fixes and patches and put out new .tgzs > I can also verify ARMedslack 11.0 works on the cirrus ebd9307A board > (using the Cirrus provided kernel patch against 2.6.20.4). Cool. I had somebody else who was going to send me some stuff for another board so I could get the installer running on it. I had a bit of a 'shock' the other day when I was reading an ARM embedded mailing list, and discovered that glibc2.7 isn't maintaining support for the ABI ARMedslack's using -- it's favouring only the new ABI. Nooooooooooooooo! :-) From mozes at slackware.com Tue May 15 16:33:31 2007 From: mozes at slackware.com (Stuart Winter) Date: Tue, 15 May 2007 09:33:31 -0700 (PDT) Subject: [armedslack] New updates uploaded Message-ID: Hi I have uploaded more updates: ftp://ftp.armedslack.org/armedslack/armedslack-current/ChangeLog.txt The big thing is that the isolinux/initrd.img (plus the one in the RiscPC !SlackBt) works! I have installed both inside QEMU and on the RiscPC. This initrd is a cpio archive rather than the loopback filesystem, so you don't need to set the ramdisk_size kernel option anymore. Enjoy! s.