VOGONS

Search

Common searches

Help me compile DOSBox with Ogg/Vorbis and a Patch.

Topic actions

First post, by James-F

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

I've been trying for 3 days to compile dosbox using MinGW according to this guide: https://www.dosbox.com/wiki/Building_DOSBox_with_MinGW

I have followed word by word using Copy and Paste (no typing) in MSYS.
There is something wrong with the OGG, Vorbis and SDL_Sound ./configure and make/ make install commands.

Everything seems to be fine here:

Admin@Desky-i7 ~/libogg-1.3.2 $ make make all-recursive make[1]: Entering directory `/home/Admin/libogg-1.3.2' Making all in sr […]
Show full quote

Admin@Desky-i7 ~/libogg-1.3.2
$ make
make all-recursive
make[1]: Entering directory `/home/Admin/libogg-1.3.2'
Making all in src
make[2]: Entering directory `/home/Admin/libogg-1.3.2/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../
include -I../include -O20 -fsigned-char -g -O2 -MT framing.lo -MD -MP -MF .de
ps/framing.Tpo -c -o framing.lo framing.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -O20 -
fsigned-char -g -O2 -MT framing.lo -MD -MP -MF .deps/framing.Tpo -c framing.c -o
framing.o
mv -f .deps/framing.Tpo .deps/framing.Plo
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../
include -I../include -O20 -fsigned-char -g -O2 -MT bitwise.lo -MD -MP -MF .de
ps/bitwise.Tpo -c -o bitwise.lo bitwise.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -O20 -
fsigned-char -g -O2 -MT bitwise.lo -MD -MP -MF .deps/bitwise.Tpo -c bitwise.c -o
bitwise.o
mv -f .deps/bitwise.Tpo .deps/bitwise.Plo
/bin/sh ../libtool --tag=CC --mode=link gcc -O20 -fsigned-char -g -O2 -no-un
defined -version-info 8:2:8 -o libogg.la -rpath /mingw/lib framing.lo bitwise.l
o
libtool: link: ar cru .libs/libogg.a framing.o bitwise.o
libtool: link: ranlib .libs/libogg.a
libtool: link: ( cd ".libs" && rm -f "libogg.la" && cp -pR "../libogg.la" "libog
g.la" )
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -D_V_SELFTEST -O20 -fsi
gned-char -g -O2 -MT test_bitwise-bitwise.o -MD -MP -MF .deps/test_bitwise-bitwi
se.Tpo -c -o test_bitwise-bitwise.o `test -f 'bitwise.c' || echo './'`bitwise.c
mv -f .deps/test_bitwise-bitwise.Tpo .deps/test_bitwise-bitwise.Po
/bin/sh ../libtool --tag=CC --mode=link gcc -D_V_SELFTEST -O20 -fsigned-char
-g -O2 -o test_bitwise.exe test_bitwise-bitwise.o
libtool: link: gcc -D_V_SELFTEST -O20 -fsigned-char -g -O2 -o test_bitwise.exe t
est_bitwise-bitwise.o
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -D_V_SELFTEST -O20 -fsi
gned-char -g -O2 -MT test_framing-framing.o -MD -MP -MF .deps/test_framing-frami
ng.Tpo -c -o test_framing-framing.o `test -f 'framing.c' || echo './'`framing.c
mv -f .deps/test_framing-framing.Tpo .deps/test_framing-framing.Po
/bin/sh ../libtool --tag=CC --mode=link gcc -D_V_SELFTEST -O20 -fsigned-char
-g -O2 -o test_framing.exe test_framing-framing.o
libtool: link: gcc -D_V_SELFTEST -O20 -fsigned-char -g -O2 -o test_framing.exe t
est_framing-framing.o
make[2]: Leaving directory `/home/Admin/libogg-1.3.2/src'
Making all in include
make[2]: Entering directory `/home/Admin/libogg-1.3.2/include'
Making all in ogg
make[3]: Entering directory `/home/Admin/libogg-1.3.2/include/ogg'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/Admin/libogg-1.3.2/include/ogg'
make[3]: Entering directory `/home/Admin/libogg-1.3.2/include'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/Admin/libogg-1.3.2/include'
make[2]: Leaving directory `/home/Admin/libogg-1.3.2/include'
Making all in doc
make[2]: Entering directory `/home/Admin/libogg-1.3.2/doc'
Making all in libogg
make[3]: Entering directory `/home/Admin/libogg-1.3.2/doc/libogg'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/Admin/libogg-1.3.2/doc/libogg'
make[3]: Entering directory `/home/Admin/libogg-1.3.2/doc'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/Admin/libogg-1.3.2/doc'
make[2]: Leaving directory `/home/Admin/libogg-1.3.2/doc'
make[2]: Entering directory `/home/Admin/libogg-1.3.2'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/home/Admin/libogg-1.3.2'
make[1]: Leaving directory `/home/Admin/libogg-1.3.2'

The problem starts with the "make install" command of the libogg-1.3.2.

Admin@Desky-i7 ~/libogg-1.3.2 $ make install Making install in src make[1]: Entering directory `/home/Admin/libogg-1.3.2/src' ma […]
Show full quote

Admin@Desky-i7 ~/libogg-1.3.2
$ make install
Making install in src
make[1]: Entering directory `/home/Admin/libogg-1.3.2/src'
make[2]: Entering directory `/home/Admin/libogg-1.3.2/src'
/bin/mkdir -p '/mingw/lib'
/bin/sh ../libtool --mode=install /bin/install -c libogg.la '/mingw/lib'
libtool: install: /bin/install -c .libs/libogg.lai /mingw/lib/libogg.la
libtool: install: /bin/install -c .libs/libogg.a /mingw/lib/libogg.a
libtool: install: chmod 644 /mingw/lib/libogg.a
libtool: install: ranlib /mingw/lib/libogg.a
/bin/sh: /home/Admin: No such file or directory
make[2]: *** [install-libLTLIBRARIES] Error 127
make[2]: Leaving directory `/home/Admin/libogg-1.3.2/src'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/home/Admin/libogg-1.3.2/src'
make: *** [install-recursive] Error 1

After that I can't ./configure Vorbis because it can't find OGG.

checking for Ogg... no *** Could not run Ogg test program, checking why... *** The test program failed to compile or link. See t […]
Show full quote

checking for Ogg... no
*** Could not run Ogg test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means Ogg was incorrectly installed
*** or that you have moved Ogg since it was installed.
configure: error: must have Ogg installed!

Obviously SDL-Sound has also errors because No Ogg or Vorbis have been installed.

If it doesn't work for me, it probably doesn't work for many other people who ignorantly following the guide word by word (like me). 😢

Anyone?


my important / useful posts are here

Reply 1 of 30, by eraH_retired

Posted on 
User metadata
Rank Retired
Rank
Retired

Not sure if this is the cause, but I think MinGW has upgraded GCC to the version 5 branch since those instructions were done.
Revert to the version 4 branch and see if that helps.

mingw-get remove gcc-g++
mingw-get install gcc-g++="4.9.*"

Let me know how you get on.

Reply 2 of 30, by Yesterplay80

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

I just tried it out: With the current GCC compiler 5.x you won't be able to compile DOSBox, as well. So either stick with 4.9 or wait for a new SVN version that's adapted to the new GCC version.

My full-featured DOSBox SVN builds for Windows & Linux: Vanilla DOSBox and DOSBox ECE (Google Drive Mirror)

Reply 3 of 30, by Dominus

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Is it the compilation or the install part a problem (as in the OP's post)?

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 30, by James-F

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

I have found a solution after many hours of tinkering.
I simply created a single name (no space) user account in windows "TEST" because when using two names with space like "First Last", OGG source don't like it.

/bin/sh: /home/First: No such file or directory

This line actually missed the last name, so I figured something is wrong with OGG source.
A simple single name user account fixed it.

Go figure... 😐


my important / useful posts are here

Reply 5 of 30, by Dominus

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Ah, good catch. Pointing at the prefix (in the configure line) with quotes around the path might have worked,too!

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 6 of 30, by James-F

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

Few questions.

Do I need to re build the libs (sound, ne, pnf, ogg, vorbis) each new SVN?
Do I need to re-apply the patch each new SVN (patch -p0 < patchname.patch)?
The compiled dosbox shows as CVS and does not use the SVN configuration I already configured, I used the link from the mingw guide while automatically downloads the latest SVN.


my important / useful posts are here

Reply 7 of 30, by Dominus

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

No, the libs only "need" to be rebuilt when these have a new version and you think you need this (but if you update a dependency you need to rebuild the dependant, e.g. if you update ogg, you will need to rebuild vorbis, sdl_sound and Dosbox).
You might need to re-apply the patch each time when the relevant parts of Dosbox got changed.

As for the conf file, no idea. Sounds as if you are using ancient dosbox sources.

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 8 of 30, by James-F

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
Dominus wrote:

As for the conf file, no idea. Sounds as if you are using ancient dosbox sources.

I just download the latest snapshot from here: http://source.dosbox.com/dosboxsvn.tgz
Should compile as SVN not CVS... no?


my important / useful posts are here

Reply 9 of 30, by Dominus

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Yeah. Does the patch maybe set this? Or does unpatched SVN also create the cvs conf?

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 10 of 30, by James-F

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

The patch I apply is the Nuked-OPL from here: AUDIO - Nuked OPL3 Patch for DOSBox(+Windows build) (SDL1)
It don't believe it should change anything besides the OPL emulation.


my important / useful posts are here

Reply 11 of 30, by Yesterplay80

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
James-F wrote:
Dominus wrote:

As for the conf file, no idea. Sounds as if you are using ancient dosbox sources.

I just download the latest snapshot from here: http://source.dosbox.com/dosboxsvn.tgz
Should compile as SVN not CVS... no?

I also noticed that when I started making regular builds: The files coming from dosbox.com all compile as CVS, while those coming from SourceForge compile as SVN. This has nothing to do with the OPL patch.

Are there really two different repositories for DOSBox? One using CVS and one using SVN?

My full-featured DOSBox SVN builds for Windows & Linux: Vanilla DOSBox and DOSBox ECE (Google Drive Mirror)

Reply 12 of 30, by Dominus

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Is the one from dosbox.com even up to date with 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 13 of 30, by Yesterplay80

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
Dominus wrote:

Is the one from dosbox.com even up to date with SVN?

No, it's obviously from September 2015. Can you tell the exact version from the code somewhere?

My full-featured DOSBox SVN builds for Windows & Linux: Vanilla DOSBox and DOSBox ECE (Google Drive Mirror)

Reply 14 of 30, by Dominus

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Not really, but looking at the file dates inside the archive should help.
So best grab the SVN, either via SVN program or let SF zip the latest source (when you look at the SVN page on SF there is anoption somewhere).
That part needs changing in the wiki, I guess.

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 15 of 30, by James-F

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

As suggested I zipped the SVN from sourceforge patched and compiled, everything is in order.
Now it uses the same config-SVN and mapper-SVN in my user folder as it should.

The wiki need these fixes:
1. Single name username for ogg or quoting the path path (that I have absolutely no idea how to do).
I really would like to stay in my "First Last" user without haveing to log off and log on to the single name user just to compile dosbox.
2. A guide to grab the latest SVN from sourceforge.
3. A guide how to apply Patches, the simple command (patch -p0 < patchname.patch) is nowhere to be found.


my important / useful posts are here

Reply 16 of 30, by Dominus

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

For the path problem you need to pass --prefix= to the configure line. I'm not on Windows anymore and it's been a while since I used mingw/msys so you will need to experiment a bit.
Something like
./configure --prefix="/home/some path/"

Might need single quotes ' instead of double quotes " and you normslly reference the path to the top folder that holds the subfolder "bin", "lib", "share" ...

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 17 of 30, by Qbix

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

Made some changes to the script on source.dosbox.com
It will now use SVN related configuration as well.

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

Reply 18 of 30, by James-F

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
Dominus wrote:

For the path problem you need to pass --prefix= to the configure line. I'm not on Windows anymore and it's been a while since I used mingw/msys so you will need to experiment a bit.
Something like
./configure --prefix="/home/some path/"

Still, "make install" command of the libogg-1.3.2 misbehaves.

EDIT:
Same thing with SDL_Net.

/bin/sh: /home/First: No such file or directory make[1]: *** [install-libLTLIBRARIES] Error 127 make[1]: Leaving directory `/hom […]
Show full quote

/bin/sh: /home/First: No such file or directory
make[1]: *** [install-libLTLIBRARIES] Error 127
make[1]: Leaving directory `/home/First Last/SDL_net-1.2.8'
make: *** [install-am] Error 2

For anti-frustration sake, can someone fix the WIKI? Please.
I'm a Copy-paster not a programmer.


my important / useful posts are here

Reply 19 of 30, by Dominus

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Where is the folder I talked about and what did you pass to 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

Go to top of page Go to top of page
Back to DOSBox Development
Close window
Close window