DSM-G600, DNS-3xx and NSA-220 Hack Forum

Ok this morning they worked. Thanks

Have you tried following instructions on page 1?

Is there a tutorial or page with instructions on how to move this to the dns-323's usbstick?

Edit:  I just made an edit to the transmission.sh script to look for the transmission folder on the usb drive.
Then I moved the folder to the usb and restarted the transmission server.  Is this all that is necessary?

Last edited by mc_365 (2014-02-23 02:18:23)

Sounds more like a network issue to me. Can you ping a web site from the console? Check your routing and DNS entries.

With transmission-daemon-c <directory>
I've solved. thanks

it's possible to compile 2.83 version ?? for ffp 0.05

Since I switched to a Zyxel NSA325 device some months ago, running with a newer Linux kernel, ffp-0.7 and a new uClibc, I don't think I can provide any compilations for ffp-0.5 anymore.

Sorry

I can try to compile for ffp-0.7 arm, but I'm not 100% sure the resulting binaries will work flawlessly on other devices, like the DNS-325.

@KyleK: chrooted ffp 0.5 runs fine on an NSA325. (Unchrooted either, but that is a bit harder to run 'in parallel'). The same is true for 0.7/oabi and 0.7/arm.

beastlord wrote:

Hi, man! And you could not throw a link to instructions for compiling transmission on ffp-0.5.
Or create a theme for the persons concerned, in which you could describe the process of building a package from source code.
I think many would be inordinately grateful.

I believe somewhere in this rather enormous thread I've already given a quick how-to to compile Transmission.

KyleK wrote:

beastlord wrote:

Hi, man! And you could not throw a link to instructions for compiling transmission on ffp-0.5.
Or create a theme for the persons concerned, in which you could describe the process of building a package from source code.
I think many would be inordinately grateful.

I believe somewhere in this rather enormous thread I've already given a quick how-to to compile Transmission.

Thnx. I'll be waiting

Winiby wrote:

KyleK wrote:

beastlord wrote:

Hi, man! And you could not throw a link to instructions for compiling transmission on ffp-0.5.
Or create a theme for the persons concerned, in which you could describe the process of building a package from source code.
I think many would be inordinately grateful.

I believe somewhere in this rather enormous thread I've already given a quick how-to to compile Transmission.

http://dns323.kood.org/forum/viewtopic. … 810#p37810

@KyleK: Hi sir, could you please share the 'configure.diff' again?

Thank you.

I spent an hour or so trying to get the environment running today. Came close but was not successful. I'll try again later in the week. Seems that some of the auto* packages are quite old versions.

KyleK wrote:

Try the packages in my repository: http://kylek.is-a-geek.org:31337/files/ffp/0.5/
I have newer versions for autoconf/automake, which should make this work

That did help, although I did manage to get around most of the errors previously by back-porting the configuration file.

However, starting clean again, I still run into issues. Can I assume that when you said run "autogen" you meant "autoscan" as I don't have "./autogen.sh"? Maybe its a script you wrote?

To summarize what I've done so far and the error (this assumes a "clean" system for a first compile):

1 - Install the various libraries. I haven't tried to narrow it down to find only the necessary ones yet. I just ran "funpkg -u *" against your files.
2 - Download and extract the transmission source
3 - Add [[   #define PACKAGE_DATA_DIR "/ffp/share" ]] to libtransmission/platform.c somewhere after the "includes"
4 - Run [[  aclocal --force  ]]
5 - Run [[  touch po/Makefile  ]]
6 - Run [[  touch po/Makefile.in  ]]
7 - Run [[  touch po/Makefilein.in  ]]
8 - Unspecified/unknown modifications to configure.ac. This may be key to getting it working??
9 - Run [[  autoscan -v  ]]
10 - Run [[  mv configure.scan configure.ac  ]]
11 - Run [[  autoheader -v -f  ]]
12 - Run [[  automake --add-missing -v  ]]
13 - Run [[  ./configure --prefix=/ffp --disable-cli --disable-gtk --disable-nls --without-inotify  ]]

The following error appears and prevents going further.
macosx/Makefile.am:174: error: BUILD_MAC does not appear in AM_CONDITIONAL

If I comment out the BUILD_MAC if/endif then it gets further. Are there any targets for "make"?


Also ./configure reports warnings, not sure if they are important to the end product:
configure: WARNING: unrecognized options: --disable-cli, --disable-gtk, --disable-nls, --without-inotify

Although it throws a warning I had to add [[  AM_INIT_AUTOMAKE([FULL-PACKAGE-NAME], [VERSION])  ]] to configure.ac to bypass other errors.

Last edited by FunFiler (2014-06-10 17:50:53)

Thanks. I will try the svn method instead of the tarball. I will compare the versions for everything else. I (we) appreciate your help. Some of us are "stuck" with 0.5

edit: Looks like I will have to find some updates.....

/mnt/HD_a2/ffp/kylek_0.5 # m4 --version
m4 (GNU M4) 1.4.10
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Rene' Seindal.
/mnt/HD_a2/ffp/kylek_0.5 # gcc --version
gcc (GCC) 4.1.3 20080414 (prerelease)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

The autogen.sh script wouldn't untar for me for some reason. Thanks for saying it was there, I found another way to extract it. Not sure why it didn't work with my usual method.


Update: autogen sure makes it easier

Last edited by FunFiler (2014-06-10 23:07:15)