On Sun, Sep 07, 2014 at 01:24:37PM +0530, Ritesh Raj Sarraf wrote:
> RPi is really turning out slow now. Packages from Wheezy are not
> serving my needs and I am forced to build newer versions.
>
> I checked local availability, and I see CubieBoard 3 available. From
> what I've looked so far, this
On Sun, 2014-09-07 at 10:29 +0200, Karsten Merker wrote:
> and WLAN (although I have not tested the latter personally).
I have, Works For Me, etc.
https://wiki.debian.org/InstallingDebianOn/Allwinner#Cubietech_Cubietruck
describes how to get the necessary firmware.
Ian.
--
To UNSUBSCRIBE, em
On Friday 05 September 2014 07:45 PM, Ritesh Raj Sarraf wrote:
On Thursday 04 September 2014 08:01 PM, Steve McIntyre wrote:
Set up a chroot using just Raspbian binaries, and build/develop in
that. It should be possible to do things directly on the Wheezy
system, but you'd have to very careful t
On Thursday 04 September 2014 08:01 PM, Steve McIntyre wrote:
Set up a chroot using just Raspbian binaries, and build/develop in
that. It should be possible to do things directly on the Wheezy
system, but you'd have to very careful to make sure no v7-only code
gets into your binaries and that's n
On Thu, Sep 04, 2014 at 06:52:52PM +0530, Ritesh Raj Sarraf wrote:
>Hi,
>
>If I set up a Debian Wheezy armhf environment, and build packages,
>why do those packages not work on Raspberry Pi ? The built package
>when run on the RPi errors out with "Illegal Instruction".
Simple: armhf is targeted at
Hi,
If I set up a Debian Wheezy armhf environment, and build packages, why
do those packages not work on Raspberry Pi ? The built package when run
on the RPi errors out with "Illegal Instruction".
I read about using the armel port, but given that RPi itself is such a
low capable hardware, an
6 matches
Mail list logo
