Compiling error with Ubuntu

[CsMisi]

Hi all, my name is Mihaly (Michael for simplicity reasons ;) ) and I'm new here (this is my first post)

I have search for a similar situation on the forum and I didn't get anything useful. So I want to join the community, and learn building Enigma2 sh4 images, especially now that there is a XBMC version on the nightlys. I have followed the installation steps.
I first run setuptdt.sh without any problems.
Than of course make.sh



Performing autogen.sh...
------------------------

I am testing that you have the required versions of libtool, autoconf,
automake, make, gettext, gcc, and g++.

checking for libtool >= 1.4.2 ... yes (version 2.4.2)
checking for autoconf >= 2.57a ... yes (version 2.69)
checking for automake >= 1.8 ... yes (version 1.14.1)
checking for gettext >= 0.12.1 ... yes (version 0.18.3)
checking for make >= 3.80 ... yes (version 3.81)
checking for gcc >= 3.0 or = 2.95 ... yes (version 4.8.2-19ubuntu1))
checking for g++ >= 3.0 or = 2.95 ... yes (version 4.8.2-19ubuntu1))

Generating configuration files for tufsbox-cdk, please wait....



Everything is OK, and as you can see it says I have autoconf 2.69

than I run
make yaud-xbmc-nightly or any other (I have tried enigma2 nightly or neutrino too)
and I got every time an error:



make[3]: Entering directory `/opt/duckbox/tdt/tdt/cvs/cdk/autoconf-2.64/doc'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/sh /opt/duckbox/tdt/tdt/cvs/cdk/autoconf-2.64/build-aux/missing --run makeinfo --version) >/dev/null 2>&1; then \
for f in autoconf.info autoconf.info-[0-9] autoconf.info-[0-9][0-9] autoconf.i[0-9] autoconf.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/sh /opt/duckbox/tdt/tdt/cvs/cdk/autoconf-2.64/build-aux/missing --run makeinfo --no-split -I . \
-o autoconf.info autoconf.texi; \
then \
rc=0; \
CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
rc=$?; \
CDPATH="${ZSH_VERSION+.}:" && cd . && \
$restore $backupdir/* `echo "./autoconf.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
conftest.c:14531: must be after `@defmac' to use `@defmacx'
make[3]: *** [autoconf.info] Error 1
make[3]: Leaving directory `/opt/duckbox/tdt/tdt/cvs/cdk/autoconf-2.64/doc'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/opt/duckbox/tdt/tdt/cvs/cdk/autoconf-2.64'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/opt/duckbox/tdt/tdt/cvs/cdk/autoconf-2.64'
make: *** [.deps/host_autoconf] Error 2


All the error messages:


/opt/duckbox/tdt/tdt/cvs/cdk/autoconf-2.64/build-aux/missing: line 52: aclocal-1.11: command not found
WARNING: `aclocal-1.11' is missing on your system. You should only need it if
you modified `acinclude.m4' or `configure.ac'. You might want
to install the `Automake' and `Perl' packages. Grab them from
any GNU archive site.
/opt/duckbox/tdt/tdt/cvs/cdk/autoconf-2.64/build-aux/missing: line 52: automake-1.11: command not found
WARNING: `automake-1.11' is missing on your system. You should only need it if
you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
You might want to install the `Automake' and `Perl' packages.
Grab them from any GNU archive site.
aclocal.m4:16: warning: this file was generated for autoconf 2.64.
You have another version of autoconf. It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
conftest.c:14531: must be after `@defmac' to use `@defmacx'
make[3]: *** [autoconf.info] Error 1
make[2]: *** [install-recursive] Error 1
make[1]: *** [install] Error 2
make: *** [.deps/host_autoconf] Error 2




My biggest problem is that as you see it is using autoconf 2.64 and not 2.69 as it is installed on my system and recognized correctly by the make.sh4 script.

Did any of you meet this error? What am I doing wrong?
I have a Ubuntu 14.04 as my main OS, but I have also started to install Ubuntu 9.10 (no more updates, so I cannot download dependecies), Fedora 12 and Fedora 20 but still, the same error. I might be looking in thw wrong place or something.
I really want to learn to do this, and make a contribution to the XBMC part, but I cannot even make a minimal new image ...
The error " must be after `@defmac' to use `@defmacx'" is an autoconf 2.64 error, 2.69 does not have this, but still the make image uses 2.64 for some reason.
Also I can see some strange error on the

Any help would pe appreciated.

[DboxOldie]

Ubuntu 14.04 don´t work > I use Ubuntu 12.04 LTS, but....
I don´t know if tdt-git works anymore, for a long time I never use it....
Use a clone of max-tdt, and after checking out perform setuptdt.sh
Note :
the master branch is for Neutrino...
the enigma2 branch is for Enigma2...
XBMC > don´t know

[jaro44]

Ubuntu 14.04 don´t work > I use Ubuntu 12.04 LTS


I now have Ubuntu 14.04 32bit and compiles fine, the problem is probably only with 64bit
(I use a clone of max-td)

[CsMisi]

And so it is. It is a x64 problem, just so everybody knows. Now I have to make a triple boot system. An x32 Linux and x64 Linux and a Windows 8.1 :)

- - - Aktualisiert - - -

Thank you for the ideas/answers

[morly]

I have my main Linux x64 bit system and all other OS's just running in vmware ;)

[jteeuw]

Hi ,

I want to compile my own version of hdmu spark 7162 , but where do i begin?

thanks

[jteeuw]

I found a wiki , i will start here :

https://gitorious.org/open-duckbox-project-sh4/pages/Installation


Hi ,

I want to compile my own version of hdmu spark 7162 , but where do i begin?

thanks

[Audioniek]

@jteeuw

Hello,

There are several git sites you can build from. The one you have shown is one of the oldest, but is sometimes not well maintained. This is a better choice to build from: https://gitorious.org/open-duckbox-project-sh4/max-tdt/source/2b856d22b45a43a7fad356d7277572db652eb2a3:. Use the enigma2 branch to build enigma2, and master for neutrino.

Another source for ideas for the spark7162 are martii's git and my own (look for audionieks-git). I hope you will have as much fun as I have had so far. The Wiki you have found is rather outdated but for enigma2 still usable.

If you have any questions, I can help you on your way. I live in the Netherlands by the way.

Regards,

Audioniek.

[linch]

@audioniek
I'm testing your git for spark7162 for neutrino-mp with kernel 214-215 and with my debian7 x64 the build is ok.
The only problem is the aotom-spark that for me not working as here

http://www.hdmedia-universe.com/board/showthread.php?6168-sparks7162-Problem-with-vfd-in-some-Amiko-Alien2
On master-tdt is working well with osaya patch

https://gitorious.org/open-duckbox-project-sh4/tdt/commit/7eca3d17f5cfc9ab236e2008e29016d665b90cc3
if you can investigate on it will be appreciated.
Many thanks for your public work and best regards.

[Audioniek]

@linch
My problem here is that I do not have receiver with the new display, so I cannot test. I changed quite a lot in aotom-spark (as you may have noticed), and the osaya-patch (adding the display type DVFD) should be in. In fact I am looking for somebody who can tell me the visible difference(s) between the old an new display from the outside, so I can shop for new one. The retailers I have spoken to so far all claim nothing has been changed in this respect, but that cannot be true.

I have the impression that the text part of the VFD has been changed from segments (comprised of dots) to complete rectangular dot fields, to the difference should e visible using a flashlight.

I will try and investigate/solve the problem as soon as I can test it.

Regards,

Audioniek.

[linch]

@linch
My problem here is that I do not have receiver with the new display, so I cannot test. I changed quite a lot in aotom-spark (as you may have noticed), and the osaya-patch (adding the display type DVFD) should be in. In fact I am looking for somebody who can tell me the visible difference(s) between the old an new display from the outside, so I can shop for new one. The retailers I have spoken to so far all claim nothing has been changed in this respect, but that cannot be true.

I have the impression that the text part of the VFD has been changed from segments (comprised of dots) to complete rectangular dot fields, to the difference should e visible using a flashlight.

I will try and investigate/solve the problem as soon as I can test it.

Regards,

Audioniek.

When i see the aotom-spark change on your git i test new code and report here.
Many thanks for the answer and best regards.