I've tried installing sdl/sdl-mixer and all other required libs/programs via macports and the stable/unstable branches of fink and nothing seems to work.
/autogen.sh
configure.ac:306: warning: macro `AM_PATH_SDL' not found in library
You should update your `aclocal.m4' by running aclocal.
configure.ac:22: installing `./missing'
configure.ac:22: installing `./install-sh'
configure.ac:306: error: possibly undefined macro: AM_PATH_SDL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
You are now ready to run ./configure
and when I run configure it halts here:
checking for special X11 libraries... no
./configure: line 20079: syntax error near unexpected token `$SDL_VERSION,'
./configure: line 20079: `AM_PATH_SDL($SDL_VERSION,'
Can anyone help? I'm dying to try the cvs on my macbook.
Cannot compile CVS on MacOSX 1.6
Forum rules
NOTICE: This forum is archived as read only.
Please use the Github Discussions at https://github.com/exult/exult/discussions
NOTICE: This forum is archived as read only.
Please use the Github Discussions at https://github.com/exult/exult/discussions
Re: Cannot compile CVS on MacOSX 1.6
Hi,
first of all, if you are not really sure what you are doing, you really shouldn't use both Fink and MacPorts at the same time. If you know what you are doing you can use either one and build all necessary stuff in EACH.
So make sure you use either MacPorts or Fink.
I use MacPorts, so my instructions will be MacPorts instructions.
Also make sure you grab the SVN of Exult and not the CVS. We switched to SVN some time ago and I *think* you meant SVN but needed to make sure
(and yeah, I need to make sure all other documentation points to SVN, too, for example ReadMe.MacOSX
)
- edit your ~/.profile and add the lines (if they haven't been there before)
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
export CFLAGS=-I/opt/local/include
export LDFLAGS=-L/opt/local/lib
export CXXFLAGS=$CFLAGS
export CPPFLAGS=$CXXFLAGS
export ACLOCAL_FLAGS="-I /opt/local/share/aclocal"
export PKG_CONFIG_PATH="/opt/local/lib/pkgconfig"
- through MacPorts grab libsdl, libsdl_mixer, automake and libtool
- in your checked out Exult's SVN edit autogen.sh and replace libtool/libtoolize with glibtool/glibtoolize
NOW it *should* work...
I haven't tested compiling with Marzo's changes from yesterday but before that, compiling under OSX 10.6.2 worked for me.
If you have a real MT32 hooked up to your Mac and you want to have it working with Exult, you also need the patch I, or more precise Willem and Marzo helped a lot and made most of it, made http://sourceforge.net/tracker/?func=de ... tid=302335
Current issues of Exult under OS X 10.6.x
- switching from windowed and fullscreen mode does not work during playing. Switching in the menu and then restarting Exult does work.
- The scalers point, interlaced, scale2x do currently not work correctly in fullscreen mode. In fact if you DON'T have an ATI graphics chip in your Mac, I'd really like to know how it works/looks for you.
These issues are somehow caused by SDL which seems to trigger a bug somewhere...
first of all, if you are not really sure what you are doing, you really shouldn't use both Fink and MacPorts at the same time. If you know what you are doing you can use either one and build all necessary stuff in EACH.
So make sure you use either MacPorts or Fink.
I use MacPorts, so my instructions will be MacPorts instructions.
Also make sure you grab the SVN of Exult and not the CVS. We switched to SVN some time ago and I *think* you meant SVN but needed to make sure

(and yeah, I need to make sure all other documentation points to SVN, too, for example ReadMe.MacOSX

- edit your ~/.profile and add the lines (if they haven't been there before)
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
export CFLAGS=-I/opt/local/include
export LDFLAGS=-L/opt/local/lib
export CXXFLAGS=$CFLAGS
export CPPFLAGS=$CXXFLAGS
export ACLOCAL_FLAGS="-I /opt/local/share/aclocal"
export PKG_CONFIG_PATH="/opt/local/lib/pkgconfig"
- through MacPorts grab libsdl, libsdl_mixer, automake and libtool
- in your checked out Exult's SVN edit autogen.sh and replace libtool/libtoolize with glibtool/glibtoolize
NOW it *should* work...
I haven't tested compiling with Marzo's changes from yesterday but before that, compiling under OSX 10.6.2 worked for me.
If you have a real MT32 hooked up to your Mac and you want to have it working with Exult, you also need the patch I, or more precise Willem and Marzo helped a lot and made most of it, made http://sourceforge.net/tracker/?func=de ... tid=302335
Current issues of Exult under OS X 10.6.x
- switching from windowed and fullscreen mode does not work during playing. Switching in the menu and then restarting Exult does work.
- The scalers point, interlaced, scale2x do currently not work correctly in fullscreen mode. In fact if you DON'T have an ATI graphics chip in your Mac, I'd really like to know how it works/looks for you.
These issues are somehow caused by SDL which seems to trigger a bug somewhere...
--
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!
Re: Cannot compile CVS on MacOSX 1.6
I am getting the same thing you are getting Roland.
Tried a binary of sdl and also had fink install sdl with the same results.
I will try to use MacPorts on another box.
Tried a binary of sdl and also had fink install sdl with the same results.
I will try to use MacPorts on another box.
Re: Cannot compile CVS on MacOSX 1.6
When you are using Fink you should have those lines in your .profile
export CFLAGS=-I/sw/include
export LDFLAGS=-L/sw/lib
export CXXFLAGS=$CFLAGS
export CPPFLAGS=$CXXFLAGS
export ACLOCAL_FLAGS="-I /sw/share/aclocal"
export PKG_CONFIG_PATH="/sw/lib/pkgconfig"
export CFLAGS=-I/sw/include
export LDFLAGS=-L/sw/lib
export CXXFLAGS=$CFLAGS
export CPPFLAGS=$CXXFLAGS
export ACLOCAL_FLAGS="-I /sw/share/aclocal"
export PKG_CONFIG_PATH="/sw/lib/pkgconfig"
--
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!
Re: Cannot compile CVS on MacOSX 1.6
My apologies for the lack of clarity in my original post. I only have a basic idea of what I'm doing, but I did know enough to try only one package manager at a time
When I switched back and forth I made sure to purge everything I could find.
And yes, I'm using the SVN. For some reason "CVS" is my brain's go-to acronym for version control systems.
I have added everything past PATH to my .profile and am about to edit the autogen.sh and give it a go. Will report back in this thread.
Oh, and I do have an Nvidia GeForce 9400M. I'll do my best to report any issues of graphic nature or otherwise in this thread.
Thanks for the respose!

And yes, I'm using the SVN. For some reason "CVS" is my brain's go-to acronym for version control systems.
I have added everything past PATH to my .profile and am about to edit the autogen.sh and give it a go. Will report back in this thread.
Oh, and I do have an Nvidia GeForce 9400M. I'll do my best to report any issues of graphic nature or otherwise in this thread.
Thanks for the respose!
Re: Cannot compile CVS on MacOSX 1.6
It wouldn't compile after adding the various flags to my .profile and adding a g to libtoolize. It spat out the same error after seeing a bit more activity with glibtoolize.
BUT, I went back in to autogen.sh and uncommented the second bit of code under aclocalincludes="" and edited it so it pointed to my aclocal directory like so:
if test -d "/opt/local/share/aclocal"; then
if test "/opt/local/share/aclocal" != `aclocal --print-ac-dir`; then
aclocalincludes="$aclocalincludes -I /opt/local/share/aclocal"
fi
fi
and it worked. Up until the point where I actually tried to "make" and the process quit out with:
/bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/include/SDL -D_GNU_SOURCE=1 -D_THREAD_SAFE -DMACOSX -O2 -Wno-long-long -I/opt/local/include -I/opt/local/include -I/opt/local/include -Wall -MT zip.lo -MD -MP -MF .deps/zip.Tpo -c -o zip.lo zip.c
libtool: Version mismatch error. This is libtool 2.2.4, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6b.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.4
libtool: and run autoconf again.
make[3]: *** [zip.lo] Error 63
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Stuck again, but progress has been made. Any suggestions?
BUT, I went back in to autogen.sh and uncommented the second bit of code under aclocalincludes="" and edited it so it pointed to my aclocal directory like so:
if test -d "/opt/local/share/aclocal"; then
if test "/opt/local/share/aclocal" != `aclocal --print-ac-dir`; then
aclocalincludes="$aclocalincludes -I /opt/local/share/aclocal"
fi
fi
and it worked. Up until the point where I actually tried to "make" and the process quit out with:
/bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/include/SDL -D_GNU_SOURCE=1 -D_THREAD_SAFE -DMACOSX -O2 -Wno-long-long -I/opt/local/include -I/opt/local/include -I/opt/local/include -Wall -MT zip.lo -MD -MP -MF .deps/zip.Tpo -c -o zip.lo zip.c
libtool: Version mismatch error. This is libtool 2.2.4, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6b.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.4
libtool: and run autoconf again.
make[3]: *** [zip.lo] Error 63
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Stuck again, but progress has been made. Any suggestions?
Re: Cannot compile CVS on MacOSX 1.6
Through some IRC wrangling with Dominus and a few others we have figured out what the problem was.
/opt/local/bin and sbin need to be first in your PATH so that the macports version of glibtoolize is used. Don't just add /opt/local/bin and sbin to the end of your PATH in .profile.
Fixing that, and adding a g to libtoolize in autogen.sh has produced a working copy of exult.
/opt/local/bin and sbin need to be first in your PATH so that the macports version of glibtoolize is used. Don't just add /opt/local/bin and sbin to the end of your PATH in .profile.
Fixing that, and adding a g to libtoolize in autogen.sh has produced a working copy of exult.
Re: Cannot compile CVS on MacOSX 1.6
We've battled with this on irc and found the solution.
The culprit is that the line in your .profile
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
does matter and it needs to be set in that order. You want to have the tools installed via MacPorts be called BEFORE the tools that come with Xcode.
Edit: Roland was a bit faster in writing that
The culprit is that the line in your .profile
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
does matter and it needs to be set in that order. You want to have the tools installed via MacPorts be called BEFORE the tools that come with Xcode.
Edit: Roland was a bit faster in writing that

--
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!
Re: Cannot compile CVS on MacOSX 1.6
Uninstalled fink and installed mac ports. So far so good.
I was able to create an executable.
Thanks
I was able to create an executable.
Thanks

Re: Cannot compile CVS on MacOSX 1.6
Hi. I am not skilled enough to compile stuff on my Mac, but I would really like a version of Exult 1.4. I'm dying to play through U7/SI again, but I'd like something closer to the latest version.
Any way you can share your executable?
Thanks!
Any way you can share your executable?
Thanks!
Re: Cannot compile CVS on MacOSX 1.6
Currently that is not possible. We are all not skilled enough to compile a static version of Exult. In other words, without compiling Exult yourself you won't be able to play current SVN.
But it's really not that hard to compile it
But it's really not that hard to compile it
--
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!