On Mon, Aug 25, 2014 at 3:25 PM, Jason Kridner <[email protected]> wrote:
>
>
>
> On Thu, Aug 21, 2014 at 4:58 PM, Robert Nelson <[email protected]>
> wrote:
>>
>> On Thu, Aug 21, 2014 at 3:52 PM, Robert Nelson <[email protected]>
>> wrote:
>> > On Thu, Aug 21, 2014 at 3:45 PM, Kridner, Jason <[email protected]> wrote:
>> >> looks like the last push is missing the defconfig:
>> >>
>> >> http://builds.beagleboard.org/builders/runtests/builds/6/steps/shell/logs/stdio
>> >
>> > It's being really weird:
>> >
>> > http://builds.beagleboard.org/one_line_per_build
>> >
>> > Aug 20 21:22 b14c60a94f59...successruntests #5 Build successful
>> > Aug 20 21:20 20830c6f9585...failureruntests #4 Failed shell shell_1
>> >
>> > When i pushed the branch yesterday...  It decided to build twice...
>> > The first build, took the first commit over the old branch, which
>> > failed as bb.org_defconfig is the last commit..  The second build
>> > completed correctly.
>> >
>> > Looks like build#6 is a rebuild of build#4
>> >
>> > can you add:
>>
>> actallly can you add:
>>
>> if [ -e arch/arm/configs/bb.org_defconfig ] ; then
>> config="bb.org_defconfig"
>> else
>> config="omap2plus_defconfig"
>> fi
>>
>> Regards,
>
>
> I'd prefer to generate builds that test that what we want to build, not some
> other config or nothing at all. I tried adding a 2 minute stability timer in
> hopes that would clear up it building the wrong thing.
>
> I'm thinking the next step is publishing the build somewhere. Any suggestion
> on how best to package it?

make ARCH=arm KBUILD_DEBARCH=armhf LOCALVERSION=-git<version>
CROSS_COMPILE=<bin>/arm-linux-gnueabihf- KDEB_PKGVERSION=1cross
deb-pkg

Then just copy the *.deb to an apache directory..

wget xyz.deb
sudo dpkg -i xyz.deb
sudo reboot

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to