[ARMedslack] ARM Slackware on the BeagleBoard

[Niels Horn]

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.
>
> Thanks,
> John O.
> _______________________________________________

John,

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"
  LIBDIRSUFFIX=""
<...>

Just put in the following lines:

<...>
elif [ "$ARCH" = "arm" ]; then
  SLKCFLAGS="-O2 -march=armv4t"
  LIBDIRSUFFIX=""
  ARCHQUADLET="-gnueabi"
<...>

and in the "./configure" part, change the following:

<...>
  --build=$ARCH-slackware-linux$ARCHQUADLET
<...>

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.

Niels