VOGONS


First post, by jwrichards

User metadata
Rank Newbie
Rank
Newbie

I can't figure this out.
I install MinGW-3.2.0-rc-3.exe on d:\
then install MSYS-1.0.9.exe.

So, final structure looks like:
d:\MinGW
d:\MSys\1.0\MinGW (I copied all the MinGW files here...don't know why)

d:\Msys\1.0\home\James\newcvs\
This is where I have the SDL (1.2.😎 and the latest CVS with my one small change.

alright, './configure'

==============================
James@BRAIN ~/newcvs/sdl
$ ./configure
checking build system type... i686-pc-mingw32
checking ..........
....................SHORTENED GREATLY.............
..................................depfiles commands
config.status: executing default commands
====================================

now....I 'make'

====================================
James@BRAIN ~/newcvs/sdl
$ make
Making all in src
make[1]: Entering directory `/home/James/newcvs/sdl/src'
Making all in main.................................
.................SHORTENED.......................
..........................directory `/home/James/newcvs/sdl'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/home/James/newcvs/sdl'
=========================================

Looks like it is all working okay...
now to run make install

=========================================
James@BRAIN ~/newcvs/sdl
$ make install
Making install in src
make[1]: Entering directory `/home/James/newcvs/sdl/src'
Making install in main
...........................directory `/home/James/newcvs/sdl/src/main'
......................SHORTENED........................
............. Leaving directory `/home/James/newcvs/sdl'
make[1]: Leaving directory `/home/James/newcvs/sdl'
==========================================

looks like everything is working just fine, now onto dosbox

James@BRAIN ~/newcvs
$ ls
SDL SDL-1.2.8.zip dosbox dosboxsource.zip

James@BRAIN ~/newcvs
$ cd dosbox

James@BRAIN ~/newcvs/dosbox
$ PATH=d/msys/1.0/home/James/newcvs/SDL

James@BRAIN ~/newcvs/dosbox
$ ./configure
sh: ./configure: No such file or directory

now....I know I'm missing something somewhere...somehow....it may even be rightr under my nose. In a frantic search of the message boardds and various guides.........nothing I can find. I'm thinking of trying this again with M$ VS Studio 6 Enterprise instead, but I need to know what i'm doing wrong so that I don't end up in the same situation....

Any takers???

I'm setting up a webpage with all the code from the msys screen so if there's something I missed there....

uhmmm......only 640k, huh?

Reply 1 of 13, by HunterZ

User metadata
Rank l33t++
Rank
l33t++

What are the contents of your dosbox directory?

Reply 2 of 13, by jwrichards

User metadata
Rank Newbie
Rank
Newbie

AUTHORS INSTALL THANKS configure.in scripts
COPYING Makefile.am VERSION docs src
CVS NEWS acinclude.m4 file.txt visualc
ChangeLog.bak README autogen.sh include visualc_net

uhmmm......only 640k, huh?

Reply 3 of 13, by jwrichards

User metadata
Rank Newbie
Rank
Newbie

file.txt is the DOS dir dump...d

uhmmm......only 640k, huh?

Reply 5 of 13, by HunterZ

User metadata
Rank l33t++
Rank
l33t++

I don't see a file named configure there. Maybe it will make one for you if you run ./autogen.sh first.

Reply 6 of 13, by jwrichards

User metadata
Rank Newbie
Rank
Newbie

uhm....nope.....I downloaded mine from the CVS-compile website from the AEP website.....the link from the dosbox website. I think that may be the problem. I'm going to try a different zip....

uhmmm......only 640k, huh?

Reply 7 of 13, by jwrichards

User metadata
Rank Newbie
Rank
Newbie

Compiled. But not working. I start to run a game and it crashes...shuts down. I noticed it couldn't find the SDL libraries during the ./configure command....my PATH statement is broken.

But, do you think this will go away when I get the PATH statement right?

during make command
fmopl.c:375: warning: converting to `OPL2::UINT32' from `double'

fmopl.c: In function `void OPL2::OPL_initalize(OPL2::FM_OPL*)':
fmopl.c:1304: warning: converting to `OPL2::UINT32' from `double'
fmopl.c:1307: warning: converting to `OPL2::UINT32' from `double'
fmopl.c:1312: warning: converting to `OPL2::UINT32' from `double'
fmopl.c:1314: warning: converting to `OPL2::UINT32' from `double'
In file included from adlib.cpp:72:
ymf262.c: At global scope:
ymf262.c:326: warning: converting to `THEOPL3::UINT32' from `double'
(repeats a few times)
ymf262.c:452: warning: converting to `THEOPL3::UINT8' from `double'
(repeats a few times)
ymf262.c: In function `void THEOPL3::OPL3_initalize(THEOPL3::OPL3*)':
ymf262.c:1347: warning: converting to `THEOPL3::UINT32' from `double'
ymf262.c:1350: warning: converting to `THEOPL3::UINT32' from `double'
ymf262.c:1355: warning: converting to `THEOPL3::UINT32' from `double'
ymf262.c:1357: warning: converting to `THEOPL3::UINT32' from `double'

uhmmm......only 640k, huh?

Reply 8 of 13, by HunterZ

User metadata
Rank l33t++
Rank
l33t++

Did you install the SDL libraries and .h files in MinGW/MSYS? You can get them from libsdl.org.

Reply 9 of 13, by jwrichards

User metadata
Rank Newbie
Rank
Newbie

That's where I think my problem is, or part of it atleast. I downloaded the SDL 1.2.8 source, and './configure', 'make', and 'make install'

It all seemed to work okay there. Do I need to find the new dlls and move them to some directory somewhere?

uhmmm......only 640k, huh?

Reply 10 of 13, by HunterZ

User metadata
Rank l33t++
Rank
l33t++

I've had the same problem before, and it usually means that my MinGW/MSYS install got hosed somehow. You should probably try reinstalling the latest versions of MSYS and MinGW32 available on Sourceforge.net.

I have MinGW32 installed in E:\MinGW and MSYS installed in E:\msys. My E:\msys\1.0\mingw directory exists but is empty.

You shouldn't have to move anything around manually to get DOSBox's configure script to detect the SDL libs/headers.

Another possible cause of your problem could be that SDL isn't actually building and/or instalilng correctly and you didn't notice.

Reply 11 of 13, by jwrichards

User metadata
Rank Newbie
Rank
Newbie

hmmmm.......good point on the SDL. I'll give it another go...see what happens. However, I also didn't spend my money on M$ Visual Studio 6 Enterprise for nothing.... do you think that is also good enough to compile with?

Anyway, I'll give it another go and see what happens.

Oh, and one little thing. XP doesn't require as many restarts as previous versions...do you think I should restart after installing MinGW?

uhmmm......only 640k, huh?

Reply 12 of 13, by gulikoza

User metadata
Rank Oldbie
Rank
Oldbie

First....most *nix stuff builds with the default dir /usr/local. If SDL is installing there, dosbox configure script might not find it later. Try to configure SDL with ./configure --prefix=/usr. Search for 'sdl-config' file, this is what dosbox configure script is looking for. I vaguely remember that some SDL makefile is broken and this file does not get renamed properly.

If you're using plain cvs checkout, you'll have to run ./autogen.sh first to generate configure script. MinGW default installation does not have this utils. Use the pcnwstage tarball. It's updated twice a day and already has a configure script ready.

Last time I checked VS6 was not good enough to build dosbox. The project file is quite outdated and I think there are some problems with the resulting code as well. Use VS.NET (afaik you can still get 2005 beta2 free from the Microsoft site)

Good luck 😀

(oh yeah...those compiler warnings in ymf262.c are harmless)

Reply 13 of 13, by jwrichards

User metadata
Rank Newbie
Rank
Newbie

Thank you. The advice really helps. I'll let everyone know if it all goes well. However, just under an hour ago, I found a box in my shed and when I opened it, I found a shoebox full of 3.5" floppies with old QBasic projects...one of which I want to start up again, now that I have some nice tools and new knowledge. My Dosbox stuff will be slow coming but I'll be here. If you want, you can check out what I'm doing (dosbox, or otherwise) at my site http://www.geocities.com/comatose_dreams. I think I want to be more active in the developement of dosbox....we'll see.
Thank you again.

uhmmm......only 640k, huh?