Hello
I’m attempting to build and install SDL from the source under Mac OS
X, but I’ve run into a problem.
The instructions say to "Run ‘./configure; make; make install’"
however, no configure file is present. I tried running autoconf on
configure.in, but it throws warnings about undefined macros
(AC_LIBTOOL_WIN32_DLL, AC_PROG_LIBTOOL, AM_PATH_ALSA, and
AM_PATH_ESD). I can suppress the warnings, but they result in errors
when the generated configure file is actually run.
Anybody have any suggestions?
thank you
Which version of OS X are you running? I compiled the SDL frameworks under
10.5.2 just recently. I used the xCode projects in xCode 3.1 to do so,
though.
I’m currently at work, so I can’t look up what I did at the moment, but I
don’t remember it being very difficult. Look at the README.MacOSX file for
directions. I used the xCode section of it. I did not try the
./configure;make;make install method.
-MattOn Thu, Apr 24, 2008 at 1:26 PM, Holmes Futrell wrote:
Hello
I’m attempting to build and install SDL from the source under Mac OS
X, but I’ve run into a problem.
The instructions say to "Run ‘./configure; make; make install’"
however, no configure file is present. I tried running autoconf on
configure.in, but it throws warnings about undefined macros
(AC_LIBTOOL_WIN32_DLL, AC_PROG_LIBTOOL, AM_PATH_ALSA, and
AM_PATH_ESD). I can suppress the warnings, but they result in errors
when the generated configure file is actually run.
Anybody have any suggestions?
thank you
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
The instructions say to "Run ‘./configure; make; make install’"
however, no configure file is present. I tried running autoconf on
configure.in, but it throws warnings about undefined macros
(AC_LIBTOOL_WIN32_DLL, AC_PROG_LIBTOOL, AM_PATH_ALSA, and
AM_PATH_ESD). I can suppress the warnings, but they result in errors
when the generated configure file is actually run.
Anybody have any suggestions?
If you pulled it from Subversion, run “./autogen.sh” first…it
generates the configure script.
(The prepackaged source archives have the configure script pregenerated,
Subversion checkouts do not.)
–ryan.
I’m attempting to build and install SDL from the source under Mac OS
X, but I’ve run into a problem.
Also, we have an XCode project, too…I’m not sure which makes more
sense (or which you are more comfortable using) for the iPhone work, but
both OS X build methods are maintained.
–ryan.
Hey Ryan,
Running autogen.sh did the trick, however the XCode project for the
most recent subversion checkout appears to have references to moved or
missing files all over the place (the prepackaged version is fine in
this regard). I do most of my development in XCode, so I’d definitely
be most comfortable this way.
- HolmesOn Apr 24, 2008, at 5:19 PM, Ryan C. Gordon wrote:
I’m attempting to build and install SDL from the source under Mac OS
X, but I’ve run into a problem.
Also, we have an XCode project, too…I’m not sure which makes more
sense (or which you are more comfortable using) for the iPhone work,
but
both OS X build methods are maintained.
–ryan.
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
Holmes Futrell wrote:
Running autogen.sh did the trick, however the XCode project for the
most recent subversion checkout appears to have references to moved or
missing files all over the place (the prepackaged version is fine in
this regard). I do most of my development in XCode, so I’d definitely
be most comfortable this way.
I suppose you’re talking about SDL 1.3. I have a cleaned-up version of
the Xcode project for that (being an Xcode guy myself). I can try to
make sure it’s up to date, and post it, hopefully some time this week
(gotta have a look at the keyboard stuff that was done in my absence too).
-Christian
I suppose you’re talking about SDL 1.3. I have a cleaned-up version of
the Xcode project for that (being an Xcode guy myself). I can try to
make sure it’s up to date, and post it, hopefully some time this week
(gotta have a look at the keyboard stuff that was done in my absence too).
Please do, I’ll get it checked into subversion.
Thanks!
-Sam Lantinga, Lead Software Engineer, Blizzard Entertainment
Sam Lantinga wrote:
I have a cleaned-up version of the Xcode project for that (being an
Xcode guy myself). I can try to make sure it’s up to date, and post
it, hopefully some time this week
Please do, I’ll get it checked into subversion.
After being almost done, I just discovered that Eric has beaten me to it
:). Merging his changes with mine will probably take me another while (I
don’t want to just throw away what I have without a closer review). I
also have an updated SDLTest project, and an addition to
SDL_config_macosx.h that was necessary (at least at the time I made it).
-Christian
After being almost done, I just discovered that Eric has beaten me to it
:). Merging his changes with mine will probably take me another while (I
don’t want to just throw away what I have without a closer review). I
also have an updated SDLTest project, and an addition to
SDL_config_macosx.h that was necessary (at least at the time I made it).
Eric’s changes don’t build out of the box on my system, FYI. I get a few
"unable to find SDL_config.h" errors, which is odd because most of the files
find it… ?
See ya,
-Sam Lantinga, Lead Software Engineer, Blizzard Entertainment
No, mine don’t work. They were an unfinished work-in-progress which I
packed up to help provide everybody with a better starting point in
the meantime. I was expecting you to submit yours 
-EricOn 5/4/08, Christian Walther wrote:
Sam Lantinga wrote:
I have a cleaned-up version of the Xcode project for that (being an
Xcode guy myself). I can try to make sure it’s up to date, and post
it, hopefully some time this week
Please do, I’ll get it checked into subversion.
After being almost done, I just discovered that Eric has beaten me to it
:). Merging his changes with mine will probably take me another while (I
don’t want to just throw away what I have without a closer review). I
also have an updated SDLTest project, and an addition to
SDL_config_macosx.h that was necessary (at least at the time I made it).
-Christian
Hello
I’m attempting to build and install SDL from the source under Mac OS
X, but I’ve run into a problem.
Can you try the project that was just checked into the stock SDL 1.3 code?
Thanks!
-Sam Lantinga, Lead Software Engineer, Blizzard Entertainment
Hello,
The latest from the 1.3 repository builds from the xcodeproj file
I encountered one problem, but it probably relates to the beta version
of XCode I’m using. The project settings have the PowerPC versions of
the library compiled with GCC 3.3, but when the PowerPC version is
compiled it says that:
“gcc-3.3: cannot specify -o with -c or -S and multiple compilations”
This goes away if I set the PowerPC GCC version to 4.0 instead.
thanks!
- HolmesOn May 7, 2008, at 10:10 PM, Sam Lantinga wrote:
Hello
I’m attempting to build and install SDL from the source under Mac OS
X, but I’ve run into a problem.
Can you try the project that was just checked into the stock SDL 1.3
code?
Thanks!
-Sam Lantinga, Lead Software Engineer, Blizzard Entertainment
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
Holmes Futrell wrote:
I encountered one problem, but it probably relates to the beta version
of XCode I’m using. The project settings have the PowerPC versions of
the library compiled with GCC 3.3, but when the PowerPC version is
compiled it says that:
/“gcc-3.3: cannot specify -o with -c or -S and multiple compilations”/
Hmm… it doesn’t do that here, as far as I see, and I’m using Xcode 3.1
beta too. (I haven’t tested building from a fresh checkout though.) Is
that a warning or an error? At what point does it occur?
-Christian
/“gcc-3.3: cannot specify -o with -c or -S and multiple compilations”/
Hmm… it doesn’t do that here, as far as I see, and I’m using Xcode 3.1
beta too. (I haven’t tested building from a fresh checkout though.) Is that
a warning or an error? At what point does it occur?
I get the same error on a fresh checkout, happens on compile (This is for
Framework without X11 and the error happens on every source file, 76 errors,
I only pasted one below because the rest are all the same except for the
source file):********************
/usr/bin/gcc-3.3 -x c -arch ppc -fmessage-length=0 -pipe -Wno-trigraphs
-fpascal-strings -faltivec -fasm-blocks -g -O0
"$(sdk_package_compiler_flags)
$(sdk_package_compiler_flags_$(gcc_language_dialect))
$(sdk_package_system_flags)" -mtune=G4
"-Wp,-header-mapfile,/Users/me/SDL/Xcode/SDL/build/SDL.build/Development/Framework
Without X11 Stuff (for those who didn’t install the X11 headers with
Xcode).build/SDL.hmap" -Wmost -F/Users/me/SDL/Xcode/SDL/build/Development
-I/Users/SDL/Xcode/SDL/build/Development/include
"-I/Users/me/SDL/Xcode/SDL/build/SDL.build/Development/Framework Without X11
Stuff (for those who didn’t install the X11 headers with
Xcode).build/DerivedSources" -DMAC_OS_X_VERSION_MIN_REQUIRED=1020
-fconstant-cfstrings -D__CONSTANT_CFSTRINGS__ -c
/Users/me/SDL/Xcode/SDL/…/…/src/audio/macrom/SDL_romaudio.c -o
"/Users/me/SDL/Xcode/SDL/build/SDL.build/Development/Framework Without X11
Stuff (for those who didn’t install the X11 headers with
Xcode).build/Objects-normal/ppc/SDL_romaudio.o"
gcc-3.3: cannot specify -o with -c or -S and multiple compilations
gcc-3.3: cannot specify -o with -c or -S and multiple compilations
gcc-3.3: cannot specify -o with -c or -S and multiple compilations
And that’s a mighty long framework name:
“Framework Without X11 Stuff (for those who didn’t install the X11 headers
with Xcode)”
Lucas
Hello!
It’s an error, and it occurs when compiling any of the SDL files for
PPC (it occurs 98 times). Here is more complete information for what
it’s generally doing:
CompileC “build/SDL.build/Development/Static Library.build/Objects-
normal/ppc/SDL_audio.o” /Users/hfutrell/SDL/Xcode/SDL/…/…/src/audio/
SDL_audio.c normal ppc c com.apple.compilers.gcc.3_3
cd /Users/hfutrell/SDL/Xcode/SDL
/usr/bin/gcc-3.3 -x c -arch ppc -fmessage-length=0 -pipe -Wno-
trigraphs -fpascal-strings -faltivec -fasm-blocks -g -O0 -
DSDL_VIDEO_DRIVER_DGA=1 -DSDL_VIDEO_DRIVER_X11=1 -
DSDL_VIDEO_DRIVER_X11_DGAMOUSE=1 -DSDL_VIDEO_DRIVER_X11_DYNAMIC="/usr/
X11R6/lib/libX11.6.dylib" -DSDL_VIDEO_DRIVER_X11_DYNAMIC_XEXT="/usr/
X11R6/lib/libXext.6.dylib" -DSDL_VIDEO_DRIVER_X11_DYNAMIC_XRANDR="/usr/
X11R6/lib/libXrandr.2.dylib" -DSDL_VIDEO_DRIVER_X11_DYNAMIC_XRENDER="/
usr/X11R6/lib/libXrender.1.dylib" -DSDL_VIDEO_DRIVER_X11_VIDMODE=1 -
DSDL_VIDEO_DRIVER_X11_XINERAMA=1 -DSDL_VIDEO_DRIVER_X11_XME=1 -
DSDL_VIDEO_DRIVER_X11_XRANDR=1 -DSDL_VIDEO_DRIVER_X11_XV=1 “$
(sdk_package_compiler_flags) $(sdk_package_compiler_flags_$
(gcc_language_dialect)) $(sdk_package_system_flags)” -mtune=G4 “-Wp,-
header-mapfile,/Users/hfutrell/SDL/Xcode/SDL/build/SDL.build/
Development/Static Library.build/SDL.hmap” -Wmost -F/Users/hfutrell/
SDL/Xcode/SDL/build/Development -I/Users/hfutrell/SDL/Xcode/SDL/build/
Development/include “-I/Users/hfutrell/SDL/Xcode/SDL/build/SDL.build/
Development/Static Library.build/DerivedSources” -
DMAC_OS_X_VERSION_MIN_REQUIRED=1020 -fconstant-cfstrings -
D__CONSTANT_CFSTRINGS__ -c /Users/hfutrell/SDL/Xcode/SDL/…/…/src/
audio/SDL_audio.c -o "/Users/hfutrell/SDL/Xcode/SDL/build/SDL.build/
Development/Static Library.build/Objects-normal/ppc/SDL_audio.o"
gcc-3.3: cannot specify -o with -c or -S and multiple compilations
- HolmesOn May 9, 2008, at 4:12 AM, Christian Walther wrote:
Holmes Futrell wrote:
I encountered one problem, but it probably relates to the beta
version of XCode I’m using. The project settings have the PowerPC
versions of the library compiled with GCC 3.3, but when the PowerPC
version is compiled it says that: /“gcc-3.3: cannot specify -o
with -c or -S and multiple compilations”/
Hmm… it doesn’t do that here, as far as I see, and I’m using Xcode
3.1 beta too. (I haven’t tested building from a fresh checkout
though.) Is that a warning or an error? At what point does it occur?
-Christian
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
/“gcc-3.3: cannot specify -o with -c or -S and multiple compilations”/
Hmm… it doesn’t do that here, as far as I see, and I’m using Xcode 3.1
beta too. (I haven’t tested building from a fresh checkout though.) Is
that
a warning or an error? At what point does it occur?
I get the same error on a fresh checkout, happens on compile (This is for
Framework without X11 and the error happens on every source file, 76 errors,
I only pasted one below because the rest are all the same except for the
source file):
Yeah, I saw that error too. I suspect it is an Xcode bug because I
don’t recall manually setting those specific flags anywhere. But I’m
wondering if it’s worth fixing. Will SDL 1.3 need to build/run on
anything less than 10.4? If not, we can remove all the gcc 3.3 stuff.
Already, Apple has thrown an interesting twist in that 10.5 has
introduced dual-mode garbage-collection binaries. For library and
plugin writers, these things should generally be written/built in dual
mode so the end user of the library/plugin has the ultimate say on
whether they want to use garbage collection or not for their own
stuff. Unfortunately, I don’t think you can build a dual mode binary
that works in 10.4 or before (though I haven’t tested this myself
yet). But I think it would be ultra-cool if some day somebody puts SDL
in a Core Animation layer in a garbage collected application.
And that’s a mighty long framework name:
“Framework Without X11 Stuff (for those who didn’t install the X11 headers
with Xcode)”
Crap. I thought I changed the name to use all underscores instead of
spaces. I think I encountered problems with our shell script packaging
phases because it misinterpreted the spaces in the target names.
-EricOn 5/9/08, Lucas Goss wrote:
Lucas Goss wrote:
I get the same error on a fresh checkout, happens on compile (This is
for Framework without X11 and the error happens on every source file, 76
errors, I only pasted one below because the rest are all the same except
for the source file):
/usr/bin/gcc-3.3 -x c -arch ppc -fmessage-length=0 -pipe -Wno-trigraphs
-fpascal-strings -faltivec -fasm-blocks -g -O0
"$(sdk_package_compiler_flags)
$(sdk_package_compiler_flags_$(gcc_language_dialect))
$(sdk_package_system_flags)" -mtune=G4
"-Wp,-header-mapfile,/Users/me/SDL/Xcode/SDL/build/SDL.build/Development/Framework
Without X11 Stuff (for those who didn’t install the X11 headers with
Xcode).build/SDL.hmap" -Wmost
-F/Users/me/SDL/Xcode/SDL/build/Development
-I/Users/SDL/Xcode/SDL/build/Development/include
"-I/Users/me/SDL/Xcode/SDL/build/SDL.build/Development/Framework Without
X11 Stuff (for those who didn’t install the X11 headers with
Xcode).build/DerivedSources" -DMAC_OS_X_VERSION_MIN_REQUIRED=1020
-fconstant-cfstrings -D__CONSTANT_CFSTRINGS__ -c
/Users/me/SDL/Xcode/SDL/…/…/src/audio/macrom/SDL_romaudio.c -o
"/Users/me/SDL/Xcode/SDL/build/SDL.build/Development/Framework Without
X11 Stuff (for those who didn’t install the X11 headers with
Xcode).build/Objects-normal/ppc/SDL_romaudio.o"
gcc-3.3: cannot specify -o with -c or -S and multiple compilations
gcc-3.3: cannot specify -o with -c or -S and multiple compilations
gcc-3.3: cannot specify -o with -c or -S and multiple compilations
That’s interesting. I just installed the latest iPhone SDK, and now I
get the same error. I guess it’s just a bug in that Xcode beta in that
case. (Which means we should stop discussing it here.)
For reference, here’s the successful compiler command line for the same
file in an earlier beta of Xcode 3.1 (one or two versions back, I don’t
remember exactly):
/usr/bin/gcc-3.3 -x c -arch ppc -pipe -Wno-trigraphs -fpascal-strings
-faltivec -fasm-blocks -g -O0 -fmessage-length=0 -mtune=G4
"-Wp,-header-mapfile,/Users/cwalther/SDL/Xcode/SDL/build/SDL.build/Development/Framework
Without X11 Stuff (for those who didn’t install the X11 headers with
Xcode).build/SDL.hmap" -Wmost
-F/Users/cwalther/SDL/Xcode/SDL/build/Development
-I/Users/cwalther/SDL/Xcode/SDL/build/Development/include
"-I/Users/cwalther/SDL/Xcode/SDL/build/SDL.build/Development/Framework
Without X11 Stuff (for those who didn’t install the X11 headers with
Xcode).build/DerivedSources" -DMAC_OS_X_VERSION_MIN_REQUIRED=1020
-fconstant-cfstrings -D__CONSTANT_CFSTRINGS__ -isystem
/Developer/SDKs/MacOSX10.4u.sdk/usr/include/gcc/darwin/3.3 -isystem
/Developer/SDKs/MacOSX10.4u.sdk/usr/include -c
/Users/cwalther/SDL/Xcode/SDL/…/…/src/audio/macrom/SDL_romaudio.c -o
"/Users/cwalther/SDL/Xcode/SDL/build/SDL.build/Development/Framework
Without X11 Stuff (for those who didn’t install the X11 headers with
Xcode).build/Objects-normal/ppc/SDL_romaudio.o"
I suspect what’s wrong is the “$(sdk_package_compiler_flags)
$(sdk_package_compiler_flags_$(gcc_language_dialect))
$(sdk_package_system_flags)” argument. No idea where that comes from. It
looks like it should have been expanded to something, perhaps the
-isystem arguments that are present in the old command line and not in
the new one.
-Christian
I wrote:
I guess it’s just a bug in that Xcode beta in that case.
FYI, I filed a radar on it and it just got closed as duplicate, so
hopefully this will be fixed soon.
-Christian