Thank you very much. I maybe need a 2.52 Ver.the source is here. You can download the tool chain and compile one. If I were set up i'd do it for you. Perhaps if you say which version, someone will compile an arm version for you.
http://download.transmissionbt.com/files/
It doesn't really need to be incorporated into entware. a binary will probably do.
asus ac87uWhich router?
Is, I noted this LOL. So is it no way to get an old ARM version?You can take any version of transmission ever been compiled from here. See how.
Oops, it's for MIPS. ARM archive has no other versions of transmission, sorry.
Thanks for you reply!I'm afraid no. Compilation is the only way.
They found Transmission 2.84 was very buggy, so banned this version. I didn't get the exact bug data.You might be able to get away with directly modifying the current version /opt/bin/transmission-daemon, using a binary editor. A quick and dirty hack might be easier than trying to gather all the dependent packages for compiling. How do they check the transmission version?
The OpenWrt packages pulls the Transmission source code from this place.who can help me? I cannot compile one by myself.
It gave me this error message.The OpenWrt packages pulls the Transmission source code from this place.
http://download-origin.transmissionbt.com/files/
Use the toolchain included with OpenWRT for ARMv7.
You could try to update the Makefile here:
https://github.com/zyxmon/openwrt-packages/blob/master/net/transmission/Makefile
Change these variables:
PKG_VERSION:=2.52
PKG_RELEASE:=1
PKG_MD5SUM:={TODO}
make package/transmission/compile -j1 V=s
It will have some dependent packages?
root@kouki:~/openwrt# make package/transmission/compile -j1 V=s
make[1]: Entering directory `/root/openwrt'
make[2]: Entering directory `/root/openwrt/package/libs/toolchain'
mkdir -p /root/openwrt/bin/ar71xx/packages /root/openwrt/build_dir/target-mips_34kc_musl-1.1.10/toolchain/ipkg-ar71xx/libgcc/CONTROL /root/openwrt/staging_dir/target-mips_34kc_musl-1.1.10/pkginfo
install -d -m0755 /root/openwrt/build_dir/target-mips_34kc_musl-1.1.10/toolchain/ipkg-ar71xx/libgcc/lib
cp -fpR /root/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_musl-1.1.10/lib/libgcc_s.so.* /root/openwrt/build_dir/target-mips_34kc_musl-1.1.10/toolchain/ipkg-ar71xx/libgcc/lib/
cp: cannot stat `/root/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_musl-1.1.10/lib/libgcc_s.so.*': No such file or directory
make[2]: *** [/root/openwrt/bin/ar71xx/packages/base/libgcc_unknown-1_ar71xx.ipk] Error 1
make[2]: Leaving directory `/root/openwrt/package/libs/toolchain'
make[1]: *** [package/libs/toolchain/compile] Error 2
make[1]: Leaving directory `/root/openwrt'
make: *** [package/transmission/compile] Error 2
Here is the Wiki that taught me how:It gave me this error message about MIPS.
Here is the Wiki that taught me how:
How to add a new package or rebuild the feed.
https://github.com/Entware/entware/wiki/How-to-add-a-new-package-or-rebuild-the-feed
However, the Entware project is a "Mips only" Buildroot environment. You may skip the step titled, "git clone https://github.com/Entware/entware.git", because it will not work for your ARMv7 router.
Instead, you need an ARMv7 Buildroot environment, this way:
cd
git clone https://github.com/zyxmon/entware-arm.git
cd entware-arm
make
Great, now you have a ARMv7 cross-compiler and tools to build Entware packages for the RT-AC68U router and other ARMv7 relatives.
Now, build the Entware packages this way:
cd ~/openwrt_trunk
make package/transmission/compile -j1 V=s
On Linux, these commands are equivalent. Any of them will change your current directory to the current user home directory.How can I get this 'openwrt_trunk' dir?
cd
cd ~
cd $HOME
cd
git clone https://github.com/zyxmon/entware-arm.git
cd entware-arm
make
Thanks for the patient reply! I have successfully finish build the environment.On Linux, these commands are equivalent. Any of them will change your current directory to the current user home directory.
Code:cd cd ~ cd $HOME
Now try this. Running 'make' will build the ARM toolchain and create the openwrt_trunk directory in your home directory. If you can't get this piece to work, the problem is with your Linux build environment.
Code:cd git clone https://github.com/zyxmon/entware-arm.git cd entware-arm make
make[4]: Entering directory `/home/parallels/openwrt_trunk/build_dir/target-arm-openwrt-linux-gnueabi/transmission-2.52/libtransmission'
CC announcer.o
CC announcer-http.o
CC announcer-udp.o
CC bandwidth.o
CC bencode.o
CC bitfield.o
CC blocklist.o
CC cache.o
CC clients.o
CC completion.o
CC ConvertUTF.o
CC crypto.o
CC fdlimit.o
In file included from /home/parallels/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sysroot/usr/include/bits/fcntl.h:54:0,
from /home/parallels/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sysroot/usr/include/fcntl.h:35,
from fdlimit.c:41:
/home/parallels/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sysroot/usr/include/bits/fcntl-linux.h:400:12: error: conflicting types for 'fallocate64'
extern int fallocate64 (int __fd, int __mode, __off64_t __offset,
^
fdlimit.c:30:14: note: previous declaration of 'fallocate64' was here
extern int fallocate64( int fd, int mode, uint64_t offset, uint64_t len );
^
make[4]: *** [fdlimit.o] Error 1
make[4]: Leaving directory `/home/parallels/openwrt_trunk/build_dir/target-arm-openwrt-linux-gnueabi/transmission-2.52/libtransmission'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/parallels/openwrt_trunk/build_dir/target-arm-openwrt-linux-gnueabi/transmission-2.52'
make[2]: *** [/home/parallels/openwrt_trunk/build_dir/target-arm-openwrt-linux-gnueabi/transmission-2.52/.built] Error 2
make[2]: Leaving directory `/home/parallels/openwrt_trunk/feeds/packages/net/transmission'
make[1]: *** [package/feeds/packages/transmission/compile] Error 2
make[1]: Leaving directory `/home/parallels/openwrt_trunk'
make: *** [package/transmission/compile] Error 2
Thanks for the patient reply! I have successfully finish build the environment.
And then, when I want to do de compile, I got this:
Do you know why this error shows?Code:make[4]: Entering directory `/home/parallels/openwrt_trunk/build_dir/target-arm-openwrt-linux-gnueabi/transmission-2.52/libtransmission' CC announcer.o CC announcer-http.o CC announcer-udp.o CC bandwidth.o CC bencode.o CC bitfield.o CC blocklist.o CC cache.o CC clients.o CC completion.o CC ConvertUTF.o CC crypto.o CC fdlimit.o In file included from /home/parallels/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sysroot/usr/include/bits/fcntl.h:54:0, from /home/parallels/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sysroot/usr/include/fcntl.h:35, from fdlimit.c:41: /home/parallels/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sysroot/usr/include/bits/fcntl-linux.h:400:12: error: conflicting types for 'fallocate64' extern int fallocate64 (int __fd, int __mode, __off64_t __offset, ^ fdlimit.c:30:14: note: previous declaration of 'fallocate64' was here extern int fallocate64( int fd, int mode, uint64_t offset, uint64_t len ); ^ make[4]: *** [fdlimit.o] Error 1 make[4]: Leaving directory `/home/parallels/openwrt_trunk/build_dir/target-arm-openwrt-linux-gnueabi/transmission-2.52/libtransmission' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/parallels/openwrt_trunk/build_dir/target-arm-openwrt-linux-gnueabi/transmission-2.52' make[2]: *** [/home/parallels/openwrt_trunk/build_dir/target-arm-openwrt-linux-gnueabi/transmission-2.52/.built] Error 2 make[2]: Leaving directory `/home/parallels/openwrt_trunk/feeds/packages/net/transmission' make[1]: *** [package/feeds/packages/transmission/compile] Error 2 make[1]: Leaving directory `/home/parallels/openwrt_trunk' make: *** [package/transmission/compile] Error 2
I almostly think it will success.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!