#README.COMPILATION NTOPNG HOW TO#
binutils/README-binutils-64k-pagesize.txt to know how to build a newer patched version (the procedure is very much similar to the one used to build standard packages).įor your convenience, I built version 2.0903-1 some months ago (the one provided by WD in the sources for firmware version 4.00.00-607 was 2.0425-1), here it is the link to download it: NOTE : Another important thing to note is that to build jessie packages it might be required to build a new patched version of binutils, becase the one provided by WD has become old: if a package you want to build depends on a newer version of binutils, it might download the newer unpatched version of binutils and hence produce an invalid package (i.e.: a package that won’t run properly on the My Cloud).įollow the instructions in. IMPORTANT: as usual, USE AT YOUR OWN RISK! No warranty of any kind! This will backup the original scripts as. # tar xzvf WD\ M圜loud\ 64k\ build\ patched\ scripts.tgz?dl=0 # cp build-armhf-package.sh build-armhf-package.sh.backup For instance: # cd /root/wdmc-build/64k-wheezy
To use these patched scripts, download this file:Īnd unpack it in the folder of the build environment you’re using (ex.: 64k-wheezy). in build-armhf-package.sh, the installation of the patched binutils was skipping binutils-dev package, which may be required by other packages on building (it happened to me) this may cause the download of a non-patched binutils-dev package, with the risk to obtain a non-properly built package.in setup.sh the detection of the host system architecture is broken in WD scripts this causes two problems: QEMU executable is not copied properly on the chrooted system, and hence package compiling often segfaults (manual solution provided in my original guide) also, some special mount points are not mounted and unmounted properly on each build attempt, producing annoying warnings.Improvements over the ones provided by WD: Here is the patched scripts I’m using to build packages.
0 kommentar(er)
