VOGONS


First post, by ykhwong

User metadata
Rank Oldbie
Rank
Oldbie

Few days ago, I noticed that DOSBox can't be compiled with the automake-1.14 or above.
A warning about possible foward-incompatilbity occurs while perfoming the autogen.sh.
The warning message can be referred from http://curl.haxx.se/mail/lib-2013-07/0040.html

I used the GCC and the result was the same both on Linux and OS X.
However, it can be normally compiled with the automake 1.13.2.

Reply 1 of 9, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Hmm, isn't this just a warning?
As I learnt with nuvie the subdir objects configure.ac thing messes up distclean or so...

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 2 of 9, by marooned_on_mars

User metadata
Rank Member
Rank
Member

Having the same problems as ykhwong on Debian.
It fails to compile resulting in a wall of errors and it doesn't seem to detect automake is present: make log

$ apt-cache policy automake
automake:
Installed: 1:1.14.1-3
Candidate: 1:1.14.1-3
Version table:
*** 1:1.14.1-3 0
500 http://http.debian.net/debian/ testing/main i386 Packages
100 /var/lib/dpkg/status
1:1.11.6-1 0
500 http://http.debian.net/debian/ wheezy/main i386 Packages

I guess I'll have to roll back to the wheezy package.

EDIT: rolled back and, the warning is gone but the errors are still there. *sigh*

Reply 3 of 9, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

The important part is the whole thing with autogen.sh and configure

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 4 of 9, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

And first run make distclean

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 5 of 9, by marooned_on_mars

User metadata
Rank Member
Rank
Member

Still the same thing, I ever cleared the folder's contents to make sure nothing escaped me and did it from scratch.
./configure seems to have been successful.

Reply 6 of 9, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Actually I see nothing in your log that seems to point at a problem with automake. It's probably all other things that got a higher version. Try with Dosbox SVN

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 7 of 9, by marooned_on_mars

User metadata
Rank Member
Rank
Member

Yup, that seems the case, I'll start a new if I have any further issues. SVN seems to compile fine so far (still having some missing Mesa OpenGL dev package that I need to get apparently)
Could you tell me what I can do in 0.74's case? I think I might actually need 0.74.

Reply 8 of 9, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Why do you need 0.74, another case of "this only works with old version" which almost always is not true?

To compile 0.74 you either need to backport the fixes or roll back your packages for gcc and everything else

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 9 of 9, by marooned_on_mars

User metadata
Rank Member
Rank
Member
Dominus wrote:

Why do you need 0.74, another case of "this only works with old version" which almost always is not true?

Er, it's because the SVN versions typically run slow on my older machine, no need to be so antagonistic.
Suggest anything that might make the SVN builds speedier.

Dominus wrote:

To compile 0.74 you either need to backport the fixes or roll back your packages for gcc and everything else

Which "fixes" are we talking about?