![]() ![]() If you encounter make errors, you’ll need to run below after making changes and/or reconfigurations: After make install, you can reuse them for other build plan projects. Work on the dependencies then transmission itself. Move the extracted linaro toolchain to a permanentpath: Get the rest of the dependencies required by transmission:Īpt-get -d source zlib openssl curl libevent Įxtract all the archives we have in the “./src” path:įor i in ls *.tar.*|grep -v debian do tar xf $i done If you have specific version, place it in this “./src” path. Else get them from me from my dropbox using: If you builded your own or extracted from WD’s GPL, place it in this “./src” path. Get the GCC Linaro 4.7 Toolchain, patched with 64K page memory size. Mkdir -p ~/Desktop/WDM圜loud/src cd ~/Desktop/WDM圜loud/src Setup temporaryenvironments for this session:Įxport PATH=$HOME/Desktop/WDM圜loud/toolchain/bin:$PATH Įxport PREFIX=$HOME/Desktop/WDM圜loud/usr/local Ĭreate permanentwork space and source path under home root and change to`em: Sudo apt-get -y install build-essential intltool checkinstall Install permanentnecessities for builds on the first time: ![]() GCC Linaro 4.7 Toolchain 64K page size memory - You can either:-Ī) build your own from WD’s v4 GPL source (577MB), under packages/build_tools/compilers,ī) or use their pre-built binaries within the downloaded GPL source above, under packages/build_tools/compilers/gcc-linaro-arm-linux-gnueabihf-4.01-20130116_2),Ĭ) or download the 82MB gcc-linaro archive from me, link at the steps.I’ve tried my best to validate this build guide with a clean install system and ensure every command are in order that you could just run it as a script. Lookup online guides on how to achieve this Linux setup, VM or standalone. Ubuntu i386 - 64-bit won’t work! I use Ubuntu 14.04 LTS Desktop (32-bit) setup with dynamic 30GB space VHD.So if setup and done correctly, you could just easily copy each code box as a whole including the last blank line, then paste in the terminal to execute. Yes you can see multi semicolon in a line, it’s called one-liner. Each command ends with a semicolon “ ” though not needed at every end, it is clearer.+ permanent- Changes to the host will last.Assuming anyone trying to compile this have some basic knowledge in Linux and fully aware of the usual WD’s warranty voidclauses including disclaimer from any damages that may resulted from this guide, prepare below (download links are underlined):. Almost similar with any other guides you can find online for transmission builds, but this is make it work for 64K page memory target. To get started, we need to get the package sources and build all shared dependencies manually, may vary from each build project but the end results with be just one *.dep file to be installed on the target system (WDM圜loud).īuild guide below is for latest transmission v2.84. Note that this guide is only for WD’s latest v4 firmware and may be compatible with their further releases if they decide to stick to 64K page size memory builds. So there’s no other choice but to cross-compile manually. As also reported in this thread by mauromol here, changing the compiler versions does not help either. I did not yield good results trying to rebuild the 64K binutils. ![]() It’s not universal, only in cases where WD’s script breaks or fails (from their v4 GPL source here: packages/build_tools/debian/build-armhf-package.sh).Īs reported by many, apparently the build instructions provided by WD for their latest 4.00.00-607 firmware for 64K page size memory, link above, is somewhat having issues with producing certain debs which resulted with compiler segmentation faults. Cross Compiling Transmission v2.84 with 64K page size memory patch ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |