I’ve tried to build 1.3.0 from svn today. I did a complete update to
make sure I had the correct code. I built the library and installed it
with not problems. But, then I tried to build in the test directory and
ran into a problem that has me stumped.
here is what I typed and the results:
bob at voyager:~/sdl/sdl1.3/test$ ./autogen.sh
bob at voyager:~/sdl/sdl1.3/test$ ./configure
checking build system type… x86_64-unknown-linux-gnu
checking host system type… x86_64-unknown-linux-gnu
checking for gcc… gcc
checking for C compiler default output file name… a.out
checking whether the C compiler works… yes
checking whether we are cross compiling… no
checking for suffix of executables…
checking for suffix of object files… o
checking whether we are using the GNU C compiler… yes
checking whether gcc accepts -g… yes
checking for gcc option to accept ISO C89… none needed
checking for an ANSI C-conforming const… yes
checking for sdl-config… /usr/local/bin/sdl-config
checking for SDL - version >= 1.3.0… no
*** Could not run SDL 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 SDL was incorrectly installed
*** or that you have moved SDL since it was installed. In the latter case, you
*** may want to edit the sdl-config script: /usr/local/bin/sdl-config
configure: error: *** SDL version 1.3.0 not found!
Ok, it says that sdl-config is reporting the wrong version of sdl. So, I test to see what it returns:
bob at voyager:~/sdl/sdl1.3/test$ sdl-config --version
1.3.0
bob at voyager:~/sdl/sdl1.3/test$ /usr/local/bin/sdl-config --version
1.3.0
bob at voyager:~/sdl/sdl1.3/test$ which sdl-config
/usr/local/bin/sdl-config
bob at voyager:~/sdl/sdl1.3/test$
Which pretty much proves that the correct sdl-config is installed
and it is the one that you get by default and from the install directory.
That’s not what it’s saying at all. It’s saying that the SDL test
program failed to compile or link, and to look at config.log for the
actual error. (This will involve wading through lots of garbage.)
-:sigma.SBOn Dec 11, 2007 2:21 PM, Bob Pendleton wrote:
*** Could not run SDL 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 SDL was incorrectly installed
*** or that you have moved SDL since it was installed. In the latter case, you
*** may want to edit the sdl-config script: /usr/local/bin/sdl-config
configure: error: *** SDL version 1.3.0 not found!
Ok, it says that sdl-config is reporting the wrong version of sdl.
*** Could not run SDL 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 SDL was incorrectly installed
*** or that you have moved SDL since it was installed. In the latter case, you
*** may want to edit the sdl-config script: /usr/local/bin/sdl-config
configure: error: *** SDL version 1.3.0 not found!
Ok, it says that sdl-config is reporting the wrong version of sdl.
That’s not what it’s saying at all. It’s saying that the SDL test
program failed to compile or link, and to look at config.log for the
actual error. (This will involve wading through lots of garbage.)
-:sigma.SB
Doh!
Yep, you are exactly right. And, after a half hour of trying to find the
problem in the wrong config.log file I finally found it and I have
checked in a patch that fixes the problem. There were a couple of new .h
files that didn’t get listed in Makefile.in.
Bob PendletonOn Tue, 2007-12-11 at 17:13 -0700, Solra Bizna wrote:
On Dec 11, 2007 2:21 PM, Bob Pendleton <@Bob_Pendleton> wrote:
Yep, you are exactly right. And, after a half hour of trying to find the
problem in the wrong config.log file I finally found it and I have
checked in a patch that fixes the problem. There were a couple of new .h
files that didn’t get listed in Makefile.in.
Thanks Bob!
See ya,
-Sam Lantinga, Lead Software Engineer, Blizzard Entertainment
Yep, you are exactly right. And, after a half hour of trying to find the
problem in the wrong config.log file I finally found it and I have
checked in a patch that fixes the problem. There were a couple of new .h
files that didn’t get listed in Makefile.in.
Thanks Bob!
You are welcome!
BTW, could you explain the new text event to me? I’m spending a little
time on 1.3 right now and I want to get keyboard input working on X11.
Bob PendletonOn Wed, 2007-12-12 at 21:02 -0800, Sam Lantinga wrote:
See ya,
-Sam Lantinga, Lead Software Engineer, Blizzard Entertainment
