Date: Sun, 14 Dec 2014 12:16:41 -0600 From: will cunningham <willpanther@...il.com> To: sabotage@...ts.openwall.com Subject: Re: raspberry PI kernel compile Paul, I think I did almost the same, except why did you uncomment A=1386? thanks, Will On Sun, Dec 14, 2014 at 12:09 PM, Paul Schutte <sjpschutte@...il.com> wrote: > > Hi Will, > > I have compiled sabotage successfully on the Raspberry PI model B, albeit > back in February of this year. (It took more than a week). > You must copy KEEP/config.stage0 to config and edit as per the > instructions at https://github.com/sabotage-linux/sabotage. > I just did a fresh git clone and it is busy compiling at the moment. > > Here is the changes I made to my config file: > > --- KEEP/config.stage0 2014-02-01 18:27:23.783217256 +0200 > +++ config 2014-02-01 18:29:47.166845189 +0200 > @@ -1,10 +1,10 @@ > ## set path to builddir (where you want your chroot). > -export SABOTAGE_BUILDDIR="/tmp/sabotage" > +export SABOTAGE_BUILDDIR="/home/pi/sbuild" > > ## set your arch, or try `uname -m` > -export A=i386 > +#export A=i386 > #export A=x86_64 > -#export A=arm > +export A=arm > #export A=mips > #export A=powerpc > > > > And my PI info: > root@...pberrypi:~# lsb_release -a > Distributor ID: Debian > Description: Debian GNU/Linux 7.2 (wheezy) > Release: 7.2 > Codename: wheezy > > > Regards > Paul > > On Sun, Dec 14, 2014 at 7:15 PM, will cunningham <willpanther@...il.com> > wrote: >> >> I'm trying to build Sabotage on a Raspberry PI version B inside Raspbian. >> >> It's failing at compiling the kernel with the log reading, >> >> "error: need to set ARM_ARCH to 4-7" >> >> and the next line, >> >> "cat: can't open '/src/KEEP/linux.config /src/KEEP/linux.config.armvl' : >> No such file or directory" >> >> There is a linux.config.armv6l file in /src/KEEP so it seems I need to >> set ARM_ARCH=6 somewhere? >> >> Thanks, >> >> Will >> > Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.