Literally the very next thing I tried worked. I spent the last 5 hours working on this so I'll go ahead and share what I did to fix.
First, I sourced my drivers from the following github repo.
sudo git clone https://github.com/gnab/rtl8812au.git
modified the Makefile
sudo nano Makefile
CONFIG_PLATFORM_I386_PC = n
CONFIG_PLATFORM_ARM_RPI = ...
Don't use wget to fetch files from github. Use git:
sudo apt-get install git
git clone https://github.com/richardghirst/PiBits
The file mailbox.c is right there in the repository. wget has no means to know you need it, but git does.
Important: Follow these instructions meticulously
Note: The OP is using Wheezy and the latest kernel version from raspberrypi-bootloader then is 4.1.7-v7+, while on jessie that version is 4.1.13-v7+ and that's a critical difference!
If you're going to apply these steps to your own situation, adjust the values accordingly.
Step 1: Get the git_hash from ...
Using some tips from this thread (thank you!), another Stack Overflow thread, another ARM install (on a Chromebook), and a lot of trial and error, I was able to get an RStudio Server v0.99.491 up and running on my Pi 2.
Sergio, what I think you're missing is:
Manually install pandoc.
sudo apt-get install -y pandoc
A new GWT compiler. The process below ...
First, get rid of that init script and forget about it. It's pointless in light of what it means to achieve, in addition to having been written by someone who do not understand how to achieve it properly in the first place.
You can just stick stuff like this in /etc/rc.local -- first check there's a PATH set at the top there already. If not:
From here, Willprice user say exaclty what I say in the comment :
OpenCV builds can sometimes fail due to using too many threads, try
running make instead of make -j $(nproc)
Make sure to increase your swap file size!
This should be a top level choice in the main menu of menuconfig:
[ ] Enable loadable module support
You want to select that, then there is a submenu; the defaults there are probably fine particularly if you are just building a module and not the whole kernel.
Be warned though, if the source version you are using doesn't match the kernel you want to load ...
I have recently been through this process and wanted to capture the answer for future reference. These benchmarks were taken using a regular stopwatch.
Configure: 30 minutes
Make: 80 minutes
Make Install: 1 minutes
I was building CMake version: 3.13
using the following steps:
git clone https://github.com/Kitware/CMake.git
mkdir build &&...
You need a complete kernel framework to build a kernel module. Search for Raspberry PI compiling kernel modules and you should get the drift.
Every time you update the kernel you will have to re-compile the module.
I'm going to guess you have a Mediatek wireless dongle.
Luckily, I think MrEngman publishes an up to date kernel module.
Find your kernel ...
A make which I do on a B+ takes 3 minutes. The identical make takes one minute on a Pi 2.
If your program uses threads you won't have to do anything special to use the extra cores. The main program or any of its threads which want to run will be given any available core.
I don't know if there are compilation flags which will make a difference to the ...
So I figured it out.
I just grabbed the crossbuild version of gcc (I think that is what it is)
sudo apt-get install crossbuild-essential-armhf
And then my new path is:
And the build works perfectly!
POSIX shells such as bash use $ as a unary operator to substitute the value of a named variable. A gotcha with variables is they don't have to have been declared in any particular context; you won't get an error for referring to $whatever even if a variable called whatever hasn't been previously declared or defined. It's just considered undefined. So ...
This appears to be the same issue as bug #837788 in the Debian bug tracker. It appears that this is actually by design, and Munin installed without any problems from the repo on your Pi:
On Fri, 10 Mar 2017 at 07:46:17 +0100, Stig Sandbeck Mathisen wrote:
Munin needs /run/munin created with the correct permissions.
When using sysv init, ...
The step you got stuck on is this one:
But then, some remarks in your question hint that you did not follow that exactly:
You tried to execute it with bash tbbvars.sh or sh tbbvars.sh
You tried to execute it with ./tbbvars.sh
These are all different from source.
What source does is execute code in the current process.
All the above ...
I was able to resolve my problem following the installation steps mentioned in this tutorial.
From the tutorial, I did the following (after reflashing Raspian to my SD):
$ sudo apt-get build-dep openocd
$ sudo apt-get install git
$ git clone git://git.code.sf.net/p/openocd/code openocd
$ cd openocd
$ ./configure --enable-bcm2835gpio
$ sudo ...
Your first mistake is in running rpi-update
"In normal circumstances there is NEVER a need to run rpi-update as it always gets you to the leading edge firmware and kernel and because that may be a testing version it could leave your RPi unbootable". https://www.raspberrypi.org/forums/viewtopic.php?p=916911#p916911
Even the rpi-update documentation now ...
What's happening is that because you are running silentoldconfig, you are going through the configuration again, but instead of using the TUI based menuconfig, you get to do it line-by-line -- at least for whatever bunch of lines it's decided this "oldconfig" updating requires input about. I've noticed this can be quite a few even from one minor version to ...
I use DietPi and it works fine for me. It is lightweight and includes management tools for your RPI with a list of optional downloadable software. Also, it helps with overclocking and SSH.
Another option I heard about is Void Linux. But it will not come with any assistive tools for raspberry pi specific activity.
I do not know where the error is and still cannot compile it with my script.
But using yaourt it works.
You can install opencv-contrib. The original PKGBUILD would not let you compile it because the Pi is an armv7h or armv6h architecture. But you can trick it by changing the PKGBUILD. Just add 'armv7h' 'armv6h' to arch as shown below and add the other two ...
By the looks of it, you're running the make bzimage command on your rasberrypi. The link http://www.frank-durr.de/?p=203 is for instructions as to how to cross-compile the rpi kernel (which is to say, compile the kernel on another platform, such as a PC running linux). In the instructions given, I suspect, commands beginning user@host are intended to be ...
3 years later, based on dhewlett's answer, I was able to build RStudio 1.1.463 on Raspbian Stretch. I've put it all into a docker build for easier reproducibility. It comes in several parts.
First create a build environment for RStudio. The Dockerfile.build_env looks like this:
FROM balenalib/raspberrypi3-debian:stretch-build as build_env