[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKHv7pjZTeizLZq-Ad4aoOWMuf=0s=9Bkjb9nWP03opWBB-ajw@mail.gmail.com>
Date: Tue, 16 Dec 2014 14:54:56 +0200
From: Paul Schutte <sjpschutte@...il.com>
To: sabotage@...ts.openwall.com
Subject: Re: raspberry PI kernel compile
Hi Will,
The following fixes that problem, but the kernel is still not compiling. It
is only doing the "make config" part and not compiling the kernel.
At the moment I cannot figure aout why.
Regards
Paul
--- sabotage/pkg/kernel 2014-12-14 20:00:07.201672545 +0200
+++ mnt/src/pkg/kernel 2014-12-16 14:22:53.816829564 +0200
@@ -57,35 +59,45 @@
linux_config="$linux_config $K/linux.config.armv${ARM_ARCH}l"
fi
-cat "$linux_config" > my.config
+cat $linux_config > my.config
On Tue, Dec 16, 2014 at 6:10 AM, will cunningham <willpanther@...il.com>
wrote:
> Thanks, Paul, adding the ARM_ARCH=6 seems to have worked, as the version
> error is gone. However I'm not getting past the second error with one
> change:
>
> "cat: can't open '/src/KEEP/linux.config /src/KEEP/linux.config.armv6l' :
> No such file or directory"
>
> Before adding the ARM_ARCH it was /src/KEEP/linux.config.armvl, and now
> it's arm6vl, so the config seems effective.
>
> Both files ARE there, so I'm guessing I need to make a soft link, or what?
>
> Thanks,
>
> Will
>
> On Sun, Dec 14, 2014 at 6:09 PM, will cunningham <willpanther@...il.com>
> wrote:
>>
>> That doesn't make sense; if it can read export from a script then it
>> should be available on the command line methinks.
>>
>> Anyway, it's compiling on the external hard drive now, and thanks again
>> for your help, as I've added it to the config file,
>>
>> Will
>>
>> On Sun, Dec 14, 2014 at 5:33 PM, will cunningham <willpanther@...il.com>
>> wrote:
>>>
>>> I was trying to export from the command line, but export isn't showing
>>> up on from my chrooted environment from the command line so I figured I
>>> needed to compile more of the base system, but of course I could put it in
>>> the config file instead of export from the command line.
>>>
>>> Now I'll use your method as I ran out of space as well on my sd card
>>> compiling the rest. Fortunately I bought a USB external hard drive for
>>> just this kind of thing, so I'll give it all another run installing
>>> sabotage there, and I'll put the export in the config file as you suggest.
>>>
>>> Onward,
>>>
>>> Will
>>>
>>> On Sun, Dec 14, 2014 at 4:54 PM, Paul Schutte <sjpschutte@...il.com>
>>> wrote:
>>>>
>>>> Maybe I am not on the same page as you, but it should not be a big
>>>> thing.
>>>>
>>>> In essence:
>>>>
>>>> ./enter-chroot
>>>> cd /src
>>>> vi config
>>>>
>>>> Now add "export ARM_ARCH=6" to the bottom of the file, save and exit.
>>>>
>>>> Then try:
>>>>
>>>> butch install kernel
>>>>
>>>>
>>>> Regards
>>>> Paul
>>>>
>>>> On Mon, Dec 15, 2014 at 12:43 AM, will cunningham <
>>>> willpanther@...il.com> wrote:
>>>>>
>>>>> Thanks so much Paul, I'm trying that next, but I had to compile Core
>>>>> to get export. This ain't exactly flying along, but it's pretty cool that
>>>>> once it's done we can just copy the SD card.
>>>>>
>>>>> Thanks for your help,
>>>>>
>>>>> Will
>>>>>
>>>>> On Sun, Dec 14, 2014 at 4:33 PM, Paul Schutte <sjpschutte@...il.com>
>>>>> wrote:
>>>>>>
>>>>>> I ran out of disk space while compiling.
>>>>>> I had a look at the build script and you are right.
>>>>>>
>>>>>> You have to set "export ARM_ARCH=6".
>>>>>> It looks to me that you should set it in /src/config on your target
>>>>>> filesystem.
>>>>>>
>>>>>> Regards
>>>>>> Paul
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Dec 14, 2014 at 8:16 PM, will cunningham <
>>>>>> willpanther@...il.com> wrote:
>>>>>>>
>>>>>>> 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.
