Try:
./configure [...] --with-float=soft
Thanks for the response. It didn’t fix the error. So I modified configure to do the -msoft-float. Ather that still got errors
one was problems wiht NLS. So I disabled the NLS. Then got a problem with CFLocale.h missing. So I commented out the exit 1. This allowed it to at least finish the configure. After that I had a couple pf error doing the make. But was
able to finally get it to build. All I need to do is test the build when I get the chance. Currently the device is in use.
Again thanks for the help
RAC
Thanks again. after a little trouble with inotify. I now have minidlna-1.1.4 working on both the WD My Cloud and my DNS-323 NAS.
hi.
i installed transmission for my cloud, it is very perfect 
what is the difference between twonky and minidlna ?
can you send photo about it ? i search google but icannot find about it
Both are DLNA servers. MiniDLNA is a lightweight version.
@Nazar
great work my Man
I have started hosting a reprosatory for v4+ patched software if you wish to contribute please let me know
it is on http://diaa.ni-ip.com:8080
it would be great to have your binaries there for all the people
cheers
I’m tryig to setup a debian system to do builds for the My Cloud. I have set it up to the point that I was able to build htop.
When I install the minidlna-1.1.4 source I can build it for the x86 cpu on the debian system. But when I do a chroot to the build environment. I then install the source for minidlna-1.1.4. I also think I eas able to get the correct librarys. But I don’t know for sure if they are correct. When I run the configure code it gets an error on the libavutil/avutil.h. I’ve seen where the
.deb files for the libraries have been installed but have not seen where they were obtained. How to I get the correct files to cross compile minidlna-1.1.4.
Thanks for your help
RAC
Your chroot build environment needs to have libav installed.
Below are the list I built for minidlna which you can get from the debian repo:
libavutil51
libavcodec53
libgsm1
libschroedinger
liborc
libmp3lame0
libva1
libx264
libtheora0
libxvidcore4
libvorbisenc2
libspeex1
libavformat53
libvpx1
libopenjpeg2
libdirac-encoder0
libswscale2
ffmpegthumbnailer
libffmpegthumbnailer4
libid3tag0
libvorbis0a
diaahussein wrote:
@Nazar
great work my Man
I have started hosting a reprosatory for v4+ patched software if you wish to contribute please let me know
it is on http://diaa.ni-ip.com:8080
it would be great to have your binaries there for all the people
cheers
My builds are not standardized. Most not included with the dependencies flags so not suitable for repositories. I built them as my own liking haha. I believe Fox_exe is the correct person if you would like to sync repos.
I have already syncup Fox_exe repo
I was trying to add yours too because you have some updated binaries like miniDlna 1.1.4 and 1.1.3 with the patches
Nazar78 wrote:
My builds are not standardized. Most not included with the dependencies flags so not suitable for repositories. I built them as my own liking haha. I believe Fox_exe is the correct person if you would like to sync repos.
I’v built minidlna versions 1.0.25 and 1.1.4 for the DNS-323 and for a debian 386 system with a few problems doing the configure. But in the end they all built and worked as designed. But on the debian system with the WD build that will build
htop. Even after getting the configure to work. I get dozens of errors doing the make. I know that the problem is not in the source. Its either in the config.h file or the build environment. every DPRINTF statement gets the following warning:
upnpsoap.c:1907:3: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
None of these messages occur with the other builds. I know that if I add -w to the compile statement these messages will not appear. But then I get the following errors:
upnpsoap.c:1894:24: error: invalid conversion from ‘const char*’ to ‘char*’ [-fpermissive]
My question is if htop builds what is the problem with minidlna?
Thanks RAC
htop is quite easy to build compared to minidlna. I suggest you take a look at the thread on my signature. Somewhere in it there’s a discussion about preparing debian environment for the 64k patch builds.
Please excuse my lack of knowledge on this forum. You said to see your thread on your signature? Not sure what this means. Also previously you said debian repo: ? Could you show the source.list statement for that repo?
Thanks RAC
I’m referring to the repo on a standard debian install:
deb http://ftp.debian.org/debian wheezy main
deb-src http://ftp.debian.org/debian wheezy main
This link on my signature:
Where did these deb files come from. I went thru the process to get the minidlna-1.1.4 files or I thought. I was able to
unzip and install the minidlna program but it didn’t install any of the libraries.
Did I download the wrong files?
RAC
I don’t understand, are you trying to install from the repo? From my understanding you’re trying to compile from source. This means you’ll need to also compile all the dependencies to produce the binaries.
I’m confused. Yes I’m trying to compile minidlna-1.1.4. I have actually been able to compile the program after I redid
the build setup. I was trying to build using a amd64 build environment. So I created a 32 bit environmment. It built the
first time.
On the first page of this thread it says to go to your site to get a credential. Then download the minidlna install code.
Which I did. I then installed to program to MY Cloud. When I tried to run it I was missing the libraries. In the third
entry on page one shows all of the libraries being installed. I was wondering how these libraries were being installed.
AS you klnow I have built version 1.1.4 for the DNS-323 and its working fine. I’ve now built version 1.1.4 after following the
instructions mauromol posted at http://community.wd.com/t5/WD-My-Cloud/GUIDE-Building-packages-for-the-new-firmware-someone-tried-it/m-p/770653#M18650. I only created the wheezy4k and wheezy64k folders. After following
these instructions I was able to run configure and it worked the first time after I installed the libraries. Not sure why the code fails to run on the MY Cloud. It gets a sigkill as soon as it starts to run. It dosen’t even get to trying to load the first library. It should have displayed an error that the library was missing.
Thanks RAC
You said you were missing the libraries when you tried to run MiniDLNA from my installer from the first page of this thread, which libraries were missing? What is your WDMyCloud current firmware version?
If you get SIGKILL when you try to run the ones you built on WDMyCloud, it means your 64K patch build wasn’t successful. Though it will work on the normal 4K page size kernel i.e. firmware V3.
When I did the install of minidlna-1.1.4_static.tar. It installed /etc/minidlna.conf /usr/sbin/minidland and the share/locale files. No libraries were installed. My My Cloud is version .421.
I’m not is the process of trying to build all of the dependencies. But I’m not sure what the dependencies are. I’m going to use the list of libraries installed from page 1. Either I’m not very smart or the information to build minidlna-1.1.4 is not complete. On the first page it shows the library files being installed. But does not show the command to start the install.
It would be nice to know the necesssary apt-get source command to get the necessary dependencies.
What I’ve been doing is doing a apt-cache search library name. Looking for the packages to load. Also not sure what should be in the sources.list to get the correct files for the wd build environment.
I have two 6TB clouds. Both are basic out of the box systems running -421 frimware. They both have the exact same sources.list file. But one system will install the libraries. But the other can’t find the libraries. I don’t think the sources.list file is correct. Yet when I used apt-get to install the necessary libraries. They were loaded. minidlna-1.1.4 is working on the one My Cloud.
I did the build in the 64k-wheezy folder. Are you saying that it actually built the 4k version? What tells the build to do 4k or 64k versions. Either it is a compile time option or it is based on the current compiler being used. Not sure what mistake I made while setting up the build environment. I suspected that since the program failed so quick that it might be a 4k version. I don’t know it there is a way to tell if a pogram is built using 64k or 4k.
/etc/apt/sources.list
deb http://ftp.us.debian.org/debian/ jessie main
Note, wheezy is not 64K page aligned.
##deb http://ftp.us.debian.org/debian/ wheezy main
#deb http://ftp.us.debian.org/debian/ sid main
#deb http://ftp.us.debian.org/debian/ experimental main
#deb-src http://ftp.us.debian.org/debian/ jessie main
Thanks for your help.
RAC
I think you’re confused. If you’re building a static builds (cross-compile with the 64k patched cross-tool), you should not have to install any extra debs on your WDMyCloud. Get their tar source ready extracted in your build environment before you configure MiniDLNA so the config can include them. Then if successful, proceed to make.
When you mentioned 64k-wheezy folder (think you derived from the posted guide to build 64K), and debs from the first page, this is not cross-compiling and you can’t get static builds using this method in the guide. Even for this method you will need to individually build every dependencies you see on the first page.
