[ARMedslack] ARM Slackware on the BeagleBoard
john.oyler at smartfield.com
Mon Jun 28 22:03:36 UTC 2010
I've managed to compile the watchdog daemon for it. I don't really think I'll be trying anything else more complex or unportable. Postgres is a maybe, and some ppp dialer stuff. You've helped immensely.
On Jun 28, 2010, at 1:49 PM, Niels Horn wrote:
> On Mon, Jun 28, 2010 at 3:07 PM, John Oyler <john.oyler at smartfield.com> wrote:
>> I used the instructions for formatting and configuring partitions on my SD card from the Angstrom Linux distribution. After getting that working, I decided to be a little bit bolder... I wiped the ext2 partition, and installed the Slackware minirootfs.
>> It booted just fine. While I'm not ready to try to compile the kernel for the Beagle (supposedly there are a ton of patches), I did copy Angstrom's kernel modules over to it, and they load fine as well.
>> Everything seems to work perfect, and it's the Slackware I know and love.
>> But here's the part where you can help me... I was never any good at using Slackbuild scripts before, and now when I look at them they're full of i486s and the like. Is there any sort of guide on how to build these? I'll be doing so natively (it's fairly zippy, and I have plenty of time) so there's no need for a cross-compiler.
>> John O.
> I build most packages for my ARMedslack installation using the
> SlackBuilds from SlackBuilds.org
> Most scripts have some lines like:
> if [ "$ARCH" = "i486" ]; then
> SLKCFLAGS="-O2 -march=i486 -mtune=i686"
> Just put in the following lines:
> elif [ "$ARCH" = "arm" ]; then
> SLKCFLAGS="-O2 -march=armv4t"
> and in the "./configure" part, change the following:
> Not *all* programs will compile on ARMedslack.
> I've had some problems with libraries that use in-line x86 assembler
> code that obviously will not work on an arm processor, but this is
> very rare.
> ARMedslack mailing list
> ARMedslack at lists.armedslack.org
More information about the ARMedslack