Hello !
Please remove the exit statements in SDL12/autogen.sh.
When compiling SDL on the Mac it outputs warning
lines, but to the statements it gets not to the “Please exec.
configure now”
These stat. are a really dumb way to detect errors.
CU
Please remove the exit statements in SDL12/autogen.sh.
read the mailing list archive:
When compiling SDL on the Mac it outputs warning
lines, but to the statements it gets not to the “Please exec.
configure now”
they arent warnings if the autotools exit with non-zero status
and if they are just warnings, then chances are it’s a bug in autotools
which should be reported upstream and fixed (if it hasnt been already)
These stat. are a really dumb way to detect errors.
no, it’s really dumb to ignore broken tools
-mikeOn Sat, Nov 19, 2005 at 09:06:18PM +0100, Torsten Giebl wrote:
Hello !
they arent warnings if the autotools exit with non-zero status
and if they are just warnings, then chances are it’s a bug in autotools
which should be reported upstream and fixed (if it hasnt been already)
I can test it more, but i got the latest SDL CVS version.
./autogen.sh
It did not get to the line please exec. configure now,
so i removed the exit lines, ran autogen.sh again.
./configure --enable-video-x11=no …
make
su
make install
and it worked.
I used the --enable-video-x11=no stuff, just because
at the moment with the dyn. X11 changes it did not work
on OSX.
When using autogen.sh without exit lines i get this :
c3b3bfa6:~/tmp/SDL12 wizard$ ./autogen.sh
Generating build information using aclocal, automake and autoconf
This may take a while …
configure.in:3026: OBJCDEPMODE was already defined in condition TRUE,
which implies condition AMDEP_TRUE
OBJCDEPMODE (User, where = configure.in:3026) =
{
TRUE => @OBJCDEPMODE@
}
configure.in:3026: OBJCDEPMODE was already defined in condition TRUE,
which implies condition AMDEP_TRUE
OBJCDEPMODE (User, where = configure.in:3026) =
{
TRUE => @OBJCDEPMODE@
}
Now you are ready to run ./configure
When using it with exit lines :
c3b3bfa6:~/tmp/SDL12 wizard$ ./autogen.sh
Generating build information using aclocal, automake and autoconf
This may take a while …
configure.in:3026: OBJCDEPMODE was already defined in condition TRUE,
which implies condition AMDEP_TRUE
OBJCDEPMODE (User, where = configure.in:3026) =
{
TRUE => @OBJCDEPMODE@
}
configure.in:3026: OBJCDEPMODE was already defined in condition TRUE,
which implies condition AMDEP_TRUE
OBJCDEPMODE (User, where = configure.in:3026) =
{
TRUE => @OBJCDEPMODE@
}
Do these messages display an error or just a warning ?
CU
which to me says either the automake code is broken in libsdl, or the
automake you have on your build system is broken
going by
makes me think the latter is true
-mikeOn Sun, Nov 20, 2005 at 11:32:39AM +0100, Torsten Giebl wrote:
When using autogen.sh without exit lines i get this :
c3b3bfa6:~/tmp/SDL12 wizard$ ./autogen.sh
Generating build information using aclocal, automake and autoconf
This may take a while …
configure.in:3026: OBJCDEPMODE was already defined in condition TRUE,
which implies condition AMDEP_TRUE
OBJCDEPMODE (User, where = configure.in:3026) =
{
TRUE => @OBJCDEPMODE@
}
Hello !
which to me says either the automake code is broken in libsdl, or the
automake you have on your build system is brokengoing by
http://www.devolution.com/pipermail/sdl/2005-September/070246.html
makes me think the latter is true -mike
I installed Mac OSX Tiger from scratch +
all Automatic Software Updates + XCode 2.1 from
the Apple Developer Site. I did not change
anything myself to the build system, so any other OSX
User with Tiger and XCode 2.1 should ge the same message.
CU
so ? doesnt mean the tools apple installs are bug free or up-to-date
-mikeOn Sun, Nov 20, 2005 at 02:35:23PM +0100, Torsten Giebl wrote:
which to me says either the automake code is broken in libsdl, or the
automake you have on your build system is brokengoing by
http://www.devolution.com/pipermail/sdl/2005-September/070246.html
makes me think the latter is trueI installed Mac OSX Tiger from scratch +
all Automatic Software Updates + XCode 2.1 from
the Apple Developer Site. I did not change
anything myself to the build system, so any other OSX
User with Tiger and XCode 2.1 should ge the same message.
Hello !
so ? doesnt mean the tools apple installs are bug free or up-to-date
No, no. Nobody is perfect 
It just means my system is Standard OSX
Tiger with latest stable XCode. So other Mac people
should also see these warnings/errors.
CU
as i pointed out in the mail archives in my first e-mail, other OS X
users are seeing this
-mikeOn Sun, Nov 20, 2005 at 03:33:12PM +0100, Torsten Giebl wrote:
It just means my system is Standard OSX
Tiger with latest stable XCode. So other Mac people
should also see these warnings/errors.
so ? doesnt mean the tools apple installs are bug free or up-to-date
Unlike Linux, it’s not reasonable to ask Mac developers to update their
autotools…you have to use what Apple gives you, even if it’s broken.
I don’t know if this particular issue is Apple’s bug…frankly, I’m not
sure what to actually DO about the issue (I see it too, and have been
hand-hacking Makefiles for as long as I’ve been working on SDL/osx to
work around it). If anyone actually knows what the hell is going on
there, please, send me a patch. I’ll beg if I have to.
–ryan.
i posted a patch to allow people in a situation similar to OS X to work
around it, but no one responded after i did 
this way, people with broken tools can run ./autogen.sh --force, but
people with sane systems get the sane default
-mikeOn Sun, Nov 20, 2005 at 10:49:38AM -0500, Ryan C. Gordon wrote:
so ? doesnt mean the tools apple installs are bug free or up-to-date
Unlike Linux, it’s not reasonable to ask Mac developers to update their
autotools…you have to use what Apple gives you, even if it’s broken.
this way, people with broken tools can run
./autogen.sh --force, but
people with sane systems get the sane default
Yeah, but I’d rather understand why it happens and fix it (although your
patch is appreciated!)
–ryan.