VOGONS


First post, by Serious Callers Only

User metadata
Rank Member
Rank
Member
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for ranlib... ranlib
checking for sdl-config... /usr/local/bin/sdl-config
checking for SDL - version >= 1.2.0... yes
checking SDL version only being 1.2.X... no
configure: error: Only libSDL 1.2.X supported

And my SDL:

apt-cache showpkg libsdl1.2-dev 
Package: libsdl1.2-dev
Versions:
1.2.14-6.4ubuntu3 (/var/lib/apt/lists/ubuntu.dcc.fc.up.pt_dists_precise_main_binary-amd64_Packages) (/var/lib/dpkg/status)
Description Language:
File: /var/lib/apt/lists/ubuntu.dcc.fc.up.pt_dists_precise_main_binary-amd64_Packages
MD5: 9a82f59c5790721baad7ffc5f181d3d6
Description Language: en
File: /var/lib/apt/lists/ubuntu.dcc.fc.up.pt_dists_precise_main_i18n_Translation-en
MD5: 9a82f59c5790721baad7ffc5f181d3d6


Reverse Depends:
libsdl1.2-dev:i386,libsdl1.2-dev
libtuxcap-dev,libsdl1.2-dev
libsmpeg-dev,libsdl1.2-dev 1.2.2-3.3
libsdl-ttf2.0-dev,libsdl1.2-dev 1.2.4
libsdl-sound1.2-dev,libsdl1.2-dev 1.2.0
libsdl-sge-dev,libsdl1.2-dev
libsdl-pango-dev,libsdl1.2-dev 1.2.4
libsdl-ocaml-dev,libsdl1.2-dev
libsdl-net1.2-dev,libsdl1.2-dev 1.2.14
libsdl-mixer1.2-dev,libsdl1.2-dev 1.2.14
libsdl-image1.2-dev,libsdl1.2-dev 1.2.10
libsdl-gfx1.2-dev,libsdl1.2-dev 1.2.5-3
libpt2.4.5-dev,libsdl1.2-dev
libpt-dev,libsdl1.2-dev
libpt-1.10.10-dev,libsdl1.2-dev
libparagui1.1-dev,libsdl1.2-dev
libkaya-sdl-dev,libsdl1.2-dev
libguichan-dev,libsdl1.2-dev
libghc-sdl-ttf-dev,libsdl1.2-dev
libghc-sdl-mixer-dev,libsdl1.2-dev
libghc-sdl-image-dev,libsdl1.2-dev
libghc-sdl-dev,libsdl1.2-dev
fenix-dev,libsdl1.2-dev
ats-lang-anairiats,libsdl1.2-dev
Dependencies:
1.2.14-6.4ubuntu3 - libsdl1.2debian (5 1.2.14-6.4ubuntu3) libx11-dev (0 (null)) libglu1-mesa-dev (0 (null)) libasound2-dev (0 (null)) libpulse-dev (0 (null)) libcaca-dev (0 (null)) libxt-dev (0 (null)) libxext-dev (0 (null)) libsdl-dev (0 (null)) libsdl-dev:i386 (0 (null)) libsdl-dev (0 (null)) libsdl-dev:i386 (0 (null)) libsdl1.2-dev:i386 (0 (null))
Provides:
1.2.14-6.4ubuntu3 - libsdl-dev
Reverse Provides:

trying to build a dosbox with the mt32 patch so i don't have the pain of having to start munt before playing games.

Anyway, if i can solve this; does dosbox source have a debian rules file? (I want to upload the source to a ppa i have so other people using ubuntu can download a mt32 enabled build somewhere)

Reply 1 of 14, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Check config.log I would say.
You can get a debian rules file from the debian package

Water flows down the stream
How to ask questions the smart way!

Reply 2 of 14, by Serious Callers Only

User metadata
Rank Member
Rank
Member

Hmmm.

conftest.c: In function 'blah':
conftest.c:15:2: error: #error "Only SDL 1.2 supported"
configure:4928: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "dosbox"
| #define PACKAGE_TARNAME "dosbox"
| #define PACKAGE_VERSION "SVN"
| #define PACKAGE_STRING "dosbox SVN"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define PACKAGE "dosbox"
| #define VERSION "SVN"
| /* end confdefs.h. */
|
| #include "SDL.h"
| void blah(){
| #if SDL_MINOR_VERSION != 2
| #error "Only SDL 1.2 supported"
| #endif
| ;
| }
|

Reply 3 of 14, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

check the SDL.h file and see what the version is inside ?
(it is probably at /usr/include/SDL/)

Water flows down the stream
How to ask questions the smart way!

Reply 4 of 14, by Serious Callers Only

User metadata
Rank Member
Rank
Member

/** @name Version Number
* Printable format: "%d.%d.%d", MAJOR, MINOR, PATCHLEVEL
*/
/*@{*/
#define SDL_MAJOR_VERSION 1
#define SDL_MINOR_VERSION 2
#define SDL_PATCHLEVEL 14
/*@}*/

(from /usr/include/SDL/SDL_version.h)

Reply 5 of 14, by Serious Callers Only

User metadata
Rank Member
Rank
Member

Maybe a /usr/local override?

ls /usr/local/include/
SDL SDL2

And
cat /usr/local/include/SDL/SDL_version.h | less

/* Printable format: "%d.%d.%d", MAJOR, MINOR, PATCHLEVEL
*/
#define SDL_MAJOR_VERSION 1
#define SDL_MINOR_VERSION 3
#define SDL_PATCHLEVEL 0

The sdl2 dir:
/* Printable format: "%d.%d.%d", MAJOR, MINOR, PATCHLEVEL
*/
#define SDL_MAJOR_VERSION 2
#define SDL_MINOR_VERSION 0
#define SDL_PATCHLEVEL 0

Neither of which has '1' as SDL_MINOR_VERSION though

Reply 6 of 14, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

the local override is verion 1.3.0 So select the right sdl to use
Think there is some SDLCONFIG=... or SDL-CONFIG= variable that you can set before running configure or use ./configure --help to find some sdl specific flags

Water flows down the stream
How to ask questions the smart way!

Reply 7 of 14, by Serious Callers Only

User metadata
Rank Member
Rank
Member

Yeah i deleted the stuff in that SDL version and things started working... dunno why i had it. Maybe a roguelike from svn... god i hate installing from source

Last edited by Serious Callers Only on 2012-09-27, 13:01. Edited 1 time in total.

Reply 8 of 14, by Serious Callers Only

User metadata
Rank Member
Rank
Member

Actually, it doesn't...

"gcc version 4.6.3
...
configure:3378: gcc -V >&5
gcc: error: unrecognized option '-V'
gcc: fatal error: no input files
"
one of many gcc errors on the configure. Can dosbox compile with this version?

edit: eh, it built

Reply 10 of 14, by Serious Callers Only

User metadata
Rank Member
Rank
Member

BTW:
https://launchpad.net/dosbox

This project is hosted at SourceForge (http://sourceforge.net/projects/dosbox/). The Launchpad project exists to provide a Bazaar mirror of the official Subversion repository. If any DOSBox developer wishes to take control of the Launchpad project, please contact me.

Reply 11 of 14, by Serious Callers Only

User metadata
Rank Member
Rank
Member

Qbix, this is strange (to me)
This source deb, which i stole the deb directory for my launchpad recipe;
http://ftp.de.debian.org/debian/pool/main/d/d … 3.debian.tar.gz

Doesn't build a executable when it's built.
It seems incomplete, for instance the
dosbox.install file doesn't have a location for the executable or the rules file is just
#!/usr/bin/make -f
%:
dh $@

But that is obviously not running when i try to build it with pbuilder after copying the debian dir into a dosbox clone and using debuild. Is that *actually* the debian dir that is being used to build the distro debs?

edit: never mind, problem between keyboard and chair

edit2: nope - what's not being called (even on the default rules like above) is autogen.sh... i'm confused, wasn't that supposed to be called by default?

edit3: missing automake in debian/control... how did it build before in the ubuntu buildbots?

Reply 12 of 14, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

The SVN source (directly from the SVN) has less files than an official release.
The official releases come with autogen.sh already executed.

Water flows down the stream
How to ask questions the smart way!

Reply 13 of 14, by Serious Callers Only

User metadata
Rank Member
Rank
Member

Well that explains it i guess. It's just strange that the debian 'patch' actually requires a additional manual step. Guess this is actually a dh problem because even if autotools is in the control file, autogen.sh is not called except if you add a override and do it yourself.

Reply 14 of 14, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

nah, the debian patch is created to work with official releases.

Water flows down the stream
How to ask questions the smart way!