Install issues: SDL Image

[guest_jessethemidget]

Hi! I'm trying to reinstall Wesnoth but I'm having problems. When I use ./config wesnoth-1.0... the console says that it can't find sdl image. But I installed it! i have installed runtime v1.2.4 and the developer library 1.5... is there a certain version I need or is my suse just bugged?

[fmunoz]

TRy getting the samve version in the headers and the library

[drewed]

I'm also running suse and cannot figure out how to convince configure that SDL_image exists on my system. I've tried setting environment variables I've reinstalled packages multiple times but can't seem to get anywhere with it. It may be that there is a really simple solution (e.g. I need to configure some environment variable correctly) but I'm not a genious with linux so....

Here's what I'm getting from configure

dreamscape:/home/sleepy/Documents/Downloads/wesnoth-1.0.1 # ./configure --enable-editor --enable-tools --enable-debug --with-kde
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... no
checking for msgmerge... no
checking for style of include used by make... 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 ANSI C... none needed
checking dependency style of gcc... gcc3
checking for ld used by GCC... /usr/i586-suse-linux/bin/ld
checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking whether gcc and cc understand -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for XOpenDisplay in -lX11... yes
checking for sdl-config... /usr/bin/sdl-config
checking for libpng-config... /usr/bin/libpng-config
checking for SDL - version >= 1.2.7... yes
checking for gnome-config... no
checking for kde-config... /opt/kde3/bin/kde-config
checking for libtool... /usr/bin/libtool
checking for IMG_Load in -lSDL_image... no
configure: error: *** SDL_image lib not found! Get SDL_image from
http://www.libsdl.org/projects/SDL_image/index.html

Note that configure did find the SDL libraries, its just that when it goes looking for IMG_Load it can't seem to locate the header file (at least that's what I think its having trouble finding). Any help would be much appreciated.

I'm running SuSE 10.0 on IA-32.

If more information is needed please tell me how to get it to you.

Thanks!

[Combatjuan]

You need the development libraries of SDL, Image, Mixer, Network, and TTF if I remember right. I'm not sure about Suse's naming conventions, but look for packages with similar names as SDLImage but with a -dev tacked on the end.

These are the ones that contain the headers and libraries that fmunoz was talking about.

[drewed]

You need the development libraries of SDL, Image, Mixer, Network, and TTF if I remember right. I'm not sure about Suse's naming conventions, but look for packages with similar names as SDLImage but with a -dev tacked on the end.

I'll try adding the Network and TTF packages, I have the development libraries for SDL, Image, and Mixer already. That's what worries me as it's trying to test the Image.h file which is on the system and seems unable to find it (its in /usr/local/include/SDL, libraries are in /usr/local/lib).

Again, I'll add the additional packages mentioned above and try again.

[drewed]

I'll add the additional packages mentioned above and try again.

No luck. Exact same error. Do I need to do anything windows-ish like reboot linux? --nope, tried that too. I've tried running under my user account instead of superuser and that didn't help either although that was a long shot to begin with.

Could it be that libtool isn't serving up the write information to the check for the SDL libraries?

System Info:

SuSE 10.0 on IA-32
Wesnoth: 1.0.1
gcc/g++: 4.0.2
KDE: 3.4.2
SDL: 1.2.9-1
SDL-image: 1.2.4-1
SDL-mixer: 1.2.6-1
SDL-net: 1.2.5-1
SDL-ttf: 2.0.7-1

[drewed]

System Info:

SuSE 10.0 on IA-32
Wesnoth: 1.0.1
gcc/g++: 4.0.2
KDE: 3.4.2
SDL: 1.2.9-1
SDL-image: 1.2.4-1
SDL-mixer: 1.2.6-1
SDL-net: 1.2.5-1
SDL-ttf: 2.0.7-1

When I went to post the information on my systems package versions, I noticed inconsistencies between development revisions (downloaded from libsdl.org) and binary revisions (installed by yast off the suse cd). Forcing yast to downgrade to the downloaded versions fixed the problem.

Note: to get suse to accept the downloaded rpms over the cd be sure to disable the cd in the Installation Source yast module or it will automatically install the wrong package.