[armedslack] Re: Armedslack X status

[Stuart Winter]

> I now have packages for the base of Xorg and could upload them somewhere.

OK I can provide somewhere to upload them to.

> But you will need to install them first before doing so. That's why I prefer
> building
> in QEMU, although slow the machines are disposable. You could see it more as
> some
> kind of bootstrapping like when compiling gcc.

Yeah ok cool :)  When you have finished please email me at
mozes at slackware.com and I will give you an ftp location to
upload to.

By the way - I use distcc to my x86 hosts.
On the x86 hosts I use this build script:
ftp://ftp.slackware.pl/pub/armedslack/armedslack-current/source/x-toolchain

which installs it into /opt/arm.
On the x86 host I use the Slackware distcc package and in rc.local
I put:
PATH=/opt/arm/bin /usr/bin/distccd --daemon --allow 0/0 -j20

And on the qemu host I have a wrapper script for the arm/build scripts:

#!/bin/bash

if [ -f .no-distcc ]; then
   echo "This source is not to be built with distcc (.no-distcc exists)"
   ./arm/build
 else
   if [ ! -d /tmp/DISTCC ]; then
      mkdir -p /tmp/DISTCC
      ( cd /tmp/DISTCC
        ln -vfs /usr/bin/distcc gcc
        ln -vfs /usr/bin/distcc cc
        ln -vfs /usr/bin/distcc g++
        ln -vfs /usr/bin/distcc c++
        ln -vfs /usr/bin/distcc arm-slackware-linux-c++
        ln -vfs /usr/bin/distcc arm-slackware-linux-g++
        ln -vfs /usr/bin/distcc arm-slackware-linux-gcc )
   fi
   export DISTCC_HOSTS="192.168.1.74/4 192.168.1.10/2 192.168.1.1 192.168.1.14 192.168.1.2"
   export CC=distcc
   PATH=/tmp/DISTCC:$PATH ./arm/build
fi

It's all a bit hacky but it works like a charm and the builds are much
faster! :-)

s.