Hi Lino,

According to these lines :

checking CXX...
<snip>
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... CC
checking whether we are using the GNU C++ compiler... no

The configure script has not found your C++ compiler whatever its name
is. And this isvery likely why you have :

checking for library containing glutGetModifiers... no

(i.e. you need a C++ compiler to use GLUT). This may also be the
reason why configure is failing to find OpenAL ? Anyway most
FlightGear/SimGear files are C++ so you definitely need to tell
configure what your C++ compiler command is.

Example if your compiler is 'myc++', call

./configure CXX="myc++"

Hope this helps.

Cheers,

Bertrand.

2010/3/11 Lino Herrera <lanth...@hotmail.com>:
> Hello FlightGear people!
> I'm need to install the FlightGear Simulator on a Solaris 10 system. I'm
> really newbie on this and I'm having problems with the SimGear package
> installation. When I try to configure the Simgear package (./configure), it
> throws an error with the message:
>
> "You *must* have the openal library installed on your system to
> build SimGear!".
>
> I already have installed the openal package on my system. Below show you the
> components in my /usr/local/include:
>
> -bash-3.00$ pwd
> /usr/local/include/AL
> -bash-3.00$ ls
> al.h     alc.h    alext.h  alut.h
> -bash-3.00$
>
> and I got this components in the /usr/local/lib:
>
> libalut.a                               libopenal.so
> libalut.so                              libopenal.so.1
> libalut.so.0                            libopenal.so.1.11.753
> libalut.so.0.0.0                        libosg.so
>
> This is the spool from my console when I try to configure the simgear
> package
>
> -bash-3.00$ ./configure
> checking for a BSD-compatible install... ./install-sh -c
> checking for -p flag to install... no
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /opt/sfw/bin/mkdir -p
> checking for gawk... no
> checking for mawk... no
> checking for nawk... nawk
> checking whether make sets $(MAKE)... yes
> checking CXX...
> checking CC...
> checking whether make sets $(MAKE)... (cached) yes
> checking for gcc... no
> checking for cc... cc
> 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... no
> checking whether cc accepts -g... yes
> checking for cc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of cc... none
> checking how to run the C preprocessor... cc -E
> checking for g++... no
> checking for c++... no
> checking for gpp... no
> checking for aCC... no
> checking for CC... CC
> checking whether we are using the GNU C++ compiler... no
> checking whether CC accepts -g... yes
> checking dependency style of CC... none
> checking for ranlib... ranlib
> checking for a BSD-compatible install... ./install-sh -c
> checking whether ln -s works... yes
> checking for boostlib >= 1.34.0... yes
> checking build system type... i386-pc-solaris2.10
> checking host system type... i386-pc-solaris2.10
> includedir changed to ${prefix}/include/simgear libdir is ${exec_prefix}/lib
> Building without Norman's jpeg image server support
> checking for extra include and lib directories...
>    + found /usr/X11R6/include
>    + found /usr/X11R6/lib
>    + found /usr/X11R6/bin
> checking for X... libraries , headers
> checking for gethostbyname... no
> checking for gethostbyname in -lnsl... yes
> checking for connect... no
> checking for connect in -lsocket... yes
> checking for remove... yes
> checking for shmat... yes
> checking for IceConnectionNumber in -lICE... yes
> checking for grep that handles long lines and -e... /usr/xpg4/bin/grep
> checking for egrep... /usr/xpg4/bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking pthread.h usability... yes
> checking pthread.h presence... yes
> checking for pthread.h... yes
> checking for library containing pthread_exit... none required
> checking for library containing inet_addr... -lxnet
> checking for library containing socket... none required
> checking for library containing cos... -lm
> checking for library containing XCreateWindow... -lX11
> checking for library containing XShmCreateImage... -lXext
> checking for library containing XGetExtensionVersion... -lXi
> checking for library containing IceOpenConnection... -lICE
> checking for library containing SmcOpenConnection... -lSM
> checking for library containing XtMalloc... -lXt
> checking for library containing XmuLookupStandardColormap... -lXmu
> checking for library containing glNewList... -lGL
> checking for library containing gluLookAt... -lGLU
> checking for library containing glutGetModifiers... no
> checking for library containing alGenBuffers... no
> checking for library containing alutInit... no
> You *must* have the openal library installed on your system to build
> SimGear!
> Please see README.OpenAL for more details.
> configure aborted.
>
> Can anybody tell me what's maybe wrong, please?
> Thanks in advance.
> Regards.
> Lino.
>

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users

Reply via email to