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

It is ok now, I achieved to launch ./autogen.sh but now when I try to launch ./configure I've got this:

root@NAS:/mnt/HD/HD_a2/ffp/tmp/minidlna# ./configure
checking build system type... arm-unknown-linux-uclibc
checking host system type... arm-unknown-linux-uclibc
checking target system type... arm-unknown-linux-uclibc
checking for a BSD-compatible install... /ffp/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /ffp/bin/mkdir -p
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.

And this is my config.log:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by MiniDLNA configure 1.1.0, which was
generated by GNU Autoconf 2.61.  Invocation command line was

  $ ./configure

## --------- ##
## Platform. ##
## --------- ##

hostname = NAS
uname -m = armv5tejl
uname -r = 2.6.22.18
uname -s = Linux
uname -v = #15 Wed May 25 15:23:11 CST 2011

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /opt/sbin
PATH: /opt/bin
PATH: /ffp/sbin
PATH: /usr/sbin
PATH: /sbin
PATH: /ffp/bin
PATH: /usr/bin
PATH: /bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1831: checking build system type
configure:1849: result: arm-unknown-linux-uclibc
configure:1871: checking host system type
configure:1886: result: arm-unknown-linux-uclibc
configure:1908: checking target system type
configure:1923: result: arm-unknown-linux-uclibc
configure:1966: checking for a BSD-compatible install
configure:2022: result: /ffp/bin/install -c
configure:2033: checking whether build environment is sane
configure:2076: result: yes
configure:2104: checking for a thread-safe mkdir -p
configure:2143: result: /ffp/bin/mkdir -p
configure:2156: checking for gawk
configure:2186: result: no
configure:2156: checking for mawk
configure:2186: result: no
configure:2156: checking for nawk
configure:2186: result: no
configure:2156: checking for awk
configure:2172: found /ffp/bin/awk
configure:2183: result: awk
configure:2194: checking whether make sets $(MAKE)
configure:2215: result: yes
configure:2424: checking for style of include used by make
configure:2452: result: GNU
configure:2522: checking for gcc
configure:2538: found /ffp/bin/gcc
configure:2549: result: gcc
configure:2787: checking for C compiler version
configure:2794: gcc --version >&5
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.

configure:2797: $? = 0
configure:2804: gcc -v >&5
Using built-in specs.
Target: arm-unknown-linux-uclibc
Configured with: /mnt/HD_a2/home/bob/funplug/work/gcc-4.1/gcc-4_1-branch/configure --enable-languages=c,c++ --enable-__cxa_atexit --with-local-prefix=/ffp --disable-multilib --disable-libssp --disable-libgomp --disable-libmudflap --disable-tls --with-float=soft --disable-bootstrap
Thread model: posix
gcc version 4.1.3 20080414 (prerelease)
configure:2807: $? = 0
configure:2814: gcc -V >&5
gcc: '-V' option must have argument
configure:2817: $? = 1
configure:2840: checking for C compiler default output file name
configure:2867: gcc    conftest.c  >&5
/opt/bin/ld: unrecognised emulation mode: armelf_linux
Supported emulations: armelf_linux_eabi armelfb_linux_eabi
collect2: ld returned 1 exit status
configure:2870: $? = 1
configure:2908: result:
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME "MiniDLNA"
| #define PACKAGE_TARNAME "minidlna"
| #define PACKAGE_VERSION "1.1.0"
| #define PACKAGE_STRING "MiniDLNA 1.1.0"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "minidlna"
| #define VERSION "1.1.0"
| #define _GNU_SOURCE 1
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:2915: error: C compiler cannot create executables
See `config.log' for more details.

Not possible, it's under ffp 0.5 I try to compile it here and not ffp 0.7

Last edited by R0b1n (2012-02-11 13:24:09)

ok, fixed the gcc error problem with installing 4.2.3 version (with ipkg). I had the 4.1.2 installed before (funpkg).

Now, minidlna CVS compiles but it does'n t work

/ffp/opt/optware/sbin/minidlna: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory

And there is something strange. The size of my binary is 631729 against 286015 with working stealth's one: http://numsys.eu/divers/minidlna-cvs-fr … 120211.tgz

Thanks Mijzelf, the binary is smaller when I strip it thats' right

But for the libjpeg issue I think it is a lib path configuration error when I try to compile minidlna. Just done that:

# cd /ffp/tmp
# cvs -d:pserver:anonymous@minidlna.cvs.sourceforge.net:/cvsroot/minidlna login
# cvs -z3 -d:pserver:anonymous@minidlna.cvs.sourceforge.net:/cvsroot/minidlna co -P minidlna
# cd minidlna
# ./autogen.sh
# ./configure
# make
# strip minidlna
# cp -f minidlna /ffp/opt/optware/sbin/
# sh /ffp/start/minidlna.sh start

and nothing else.

I saw that stealth done a ./configure LIBS="liconv" to compile minidlna. What's for ?

Last edited by R0b1n (2012-02-12 20:33:49)