GL/gl.h ???

Tried to build rcssserver3d using the terminal and it breaks the operation saying:

checking OpenGL/gl.h usability… no
checking OpenGL/gl.h presence… no
checking for OpenGL/gl.h… no
checking OpenGL/glu.h usability… no
checking OpenGL/glu.h presence… no
checking for OpenGL/glu.h… no
checking if I am a Mac… sorry
checking GL/gl.h usability… no
checking GL/gl.h presence… no
checking for GL/gl.h… no
configure: WARNING: not all required OpenGL headers could not be found. Please specify the location of the OpenGL header directory using the CPPFLAGS environment variable
checking GL/glu.h usability… no
checking GL/glu.h presence… no
checking for GL/glu.h… no
configure: WARNING: not all required OpenGL headers could not be found. Please specify the location of the OpenGL header directory using the CPPFLAGS environment variable
checking GL/glut.h usability… no
checking GL/glut.h presence… no
checking for GL/glut.h… no
configure: error: need GL stuff to build monitor

anybody know what this means or how can i fix it?

yes, it means that you are missing the libraries.

Try to install the glut or freeglut development packages from yast,that should contain the libraries.

HTH

Lenwolf

thank you it worked.
but now I get this error:

checking if libkerosin will be build… no
configure: error: libkerosin cannot be build without all required libraries.

On 01/31/2012 08:06 AM, vandermonde wrote:
>
>> checking if libkerosin will be build… no
>> configure: error: libkerosin cannot be build without all required
>> libraries.

just like the answer on GL/gl.h this is like: read the error!

this new error means that you are missing the libraries for libkerosin…

i do not know where they are sourced (they are not in YaST, as far as i
can see…use google or other to track them down…)


DD http://tinyurl.com/DD-Caveat
Read what Distro Watch writes: http://tinyurl.com/SUSEonDW

I think libkerosin is not a library that I should install.
libkerosin cannot be build without all required
it is the complete build process:

warning: rcssserver3d-0.6-1.1.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID a4f30edf: NOKEY
error: Failed dependencies:
mesa-libGL is needed by rcssserver3d-0.6-1.1.x86_64
mesa-libGLU is needed by rcssserver3d-0.6-1.1.x86_64
vandermonde@linux-vr80:~/Downloads> cd rcssserver3d-0.6/
vandermonde@linux-vr80:~/Downloads/rcssserver3d-0.6> ./configure
configure: loading site script /usr/share/site/x86_64-unknown-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 for g++… g++
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 g++ accepts -g… yes
checking for style of include used by make… GNU
checking dependency style of g++… gcc3
checking for gcc… gcc
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 dependency style of gcc… gcc3
checking whether gcc and cc understand -c and -o together… yes
checking for a BSD-compatible install… /usr/bin/install -c
checking build system type… x86_64-suse-linux-gnu
checking host system type… x86_64-suse-linux-gnu
checking for a sed that does not truncate output… /usr/bin/sed
checking for grep that handles long lines and -e… /usr/bin/grep
checking for egrep… /usr/bin/grep -E
checking for ld used by gcc… /usr/x86_64-suse-linux/bin/ld
checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld… yes
checking for /usr/x86_64-suse-linux/bin/ld option to reload object files… -r
checking for BSD-compatible nm… /usr/bin/nm -B
checking whether ln -s works… yes
checking how to recognise dependent libraries… pass_all
checking how to run the C preprocessor… gcc -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 dlfcn.h usability… yes
checking dlfcn.h presence… yes
checking for dlfcn.h… yes
checking how to run the C++ preprocessor… g++ -E
checking for g77… no
checking for f77… no
checking for xlf… no
checking for frt… no
checking for pgf77… no
checking for cf77… no
checking for fort77… no
checking for fl32… no
checking for af77… no
checking for f90… no
checking for xlf90… no
checking for pgf90… no
checking for pghpf… no
checking for epcf90… no
checking for gfortran… no
checking for g95… no
checking for f95… no
checking for fort… no
checking for xlf95… no
checking for ifort… no
checking for ifc… no
checking for efc… no
checking for pgf95… no
checking for lf95… no
checking for ftn… no
checking whether we are using the GNU Fortran 77 compiler… no
checking whether accepts -g… no
checking the maximum length of command line arguments… 32768
checking command to parse /usr/bin/nm -B output from gcc object… ok
checking for objdir… .libs
checking for ar… ar
checking for ranlib… ranlib
checking for strip… strip
checking if gcc supports -fno-rtti -fno-exceptions… no
checking for gcc option to produce PIC… -fPIC
checking if gcc PIC flag -fPIC works… yes
checking if gcc static flag -static works… no
checking if gcc supports -c -o file.o… yes
checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries… yes
checking whether -lc should be explicitly linked in… no
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking whether stripping libraries is possible… yes
checking for shl_load… no
checking for shl_load in -ldld… no
checking for dlopen… no
checking for dlopen in -ldl… yes
checking whether a program can dlopen itself… yes
checking whether a statically linked program can dlopen itself… yes
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… no
configure: creating libtool
appending configuration tag “CXX” to libtool
checking for ld used by g++… /usr/x86_64-suse-linux/bin/ld -m elf_x86_64
checking if the linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) is GNU ld… yes
checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries… yes
checking for g++ option to produce PIC… -fPIC
checking if g++ PIC flag -fPIC works… yes
checking if g++ static flag -static works… no
checking if g++ supports -c -o file.o… yes
checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries… yes
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
appending configuration tag “F77” to libtool
checking for gawk… (cached) gawk
checking for doxygen… yes
checking for pdflatex… no
checking for dot… YES
checking for perl… /usr/bin/perl
checking for dlopen in -ldl… (cached) yes
checking for ANSI C header files… (cached) yes
checking poll.h usability… yes
checking poll.h presence… yes
checking for poll.h… yes
checking arpa/nameser.h usability… yes
checking arpa/nameser.h presence… yes
checking for arpa/nameser.h… yes
checking arpa/inet.h usability… yes
checking arpa/inet.h presence… yes
checking for arpa/inet.h… yes
checking resolv.h usability… yes
checking resolv.h presence… yes
checking for resolv.h… yes
checking netdb.h usability… yes
checking netdb.h presence… yes
checking for netdb.h… yes
checking sys/socket.h usability… yes
checking sys/socket.h presence… yes
checking for sys/socket.h… yes
checking netinet/in.h usability… yes
checking netinet/in.h presence… yes
checking for netinet/in.h… yes
checking Winsock2.h usability… no
checking Winsock2.h presence… no
checking for Winsock2.h… no
checking float.h usability… yes
checking float.h presence… yes
checking for float.h… yes
checking limits.h usability… yes
checking limits.h presence… yes
checking for limits.h… yes
checking malloc.h usability… yes
checking malloc.h presence… yes
checking for malloc.h… yes
checking for memory.h… (cached) yes
checking for stdlib.h… (cached) yes
checking for string.h… (cached) yes
checking execinfo.h usability… yes
checking execinfo.h presence… yes
checking for execinfo.h… yes
checking CoreFoundation/CoreFoundation.h usability… no
checking CoreFoundation/CoreFoundation.h presence… no
checking for CoreFoundation/CoreFoundation.h… no
checking boost/version.hpp usability… yes
checking boost/version.hpp presence… yes
checking for boost/version.hpp… yes
checking backward/hash_map usability… yes
checking backward/hash_map presence… yes
checking for backward/hash_map… yes
checking for an ANSI C-conforming const… yes
checking for inline… inline
checking for size_t… yes
checking for socklen_t… yes
checking for working alloca.h… yes
checking for alloca… yes
checking for working memcmp… yes
checking for function prototypes… yes
checking whether setvbuf arguments are reversed… no
checking for vprintf… yes
checking for _doprnt… no
checking for _vsnprintf… no
checking for atexit… yes
checking for floor… yes
checking for gethostname… yes
checking for inet_ntoa… yes
checking for memset… yes
checking for pow… yes
checking for socket… yes
checking for sqrt… yes
checking for strchr… yes
checking for strrchr… yes
checking for strstr… yes
checking for strupr… no
checking for socket in -lsocket… no
checking for gethostbyname in -lnsl… yes
checking for sched_yield in -lposix4… no
checking for hstrerror in -lresolv… yes
checking if linking against boost_regex succeeds… no
configure: WARNING: the ZIP filesystem plugin cannot be build
checking boost thread library… -lboost_thread
checking OpenGL/gl.h usability… no
checking OpenGL/gl.h presence… no
checking for OpenGL/gl.h… no
checking OpenGL/glu.h usability… no
checking OpenGL/glu.h presence… no
checking for OpenGL/glu.h… no
checking if I am a Mac… sorry
checking GL/gl.h usability… yes
checking GL/gl.h presence… yes
checking for GL/gl.h… yes
checking GL/glu.h usability… yes
checking GL/glu.h presence… yes
checking for GL/glu.h… yes
checking GL/glut.h usability… yes
checking GL/glut.h presence… yes
checking for GL/glut.h… yes
checking for GL/glx.h… yes
checking if linking against libGL succeeds… yes
checking if linking against libGLU succeeds… yes
checking if linking against libglut succeeds… yes
configure: Checking prerequisites for kerosin…
checking for X… libraries /usr/lib64, headers
checking for OpenGL/gl.h… (cached) no
checking for OpenGL/glu.h… (cached) no
checking if I am a Mac… sorry
checking for GL/gl.h… (cached) yes
checking for GL/glu.h… (cached) yes
checking for GL/glut.h… (cached) yes
checking for GL/glx.h… (cached) yes
checking if linking against libGL succeeds… yes
checking if linking against libGLU succeeds… yes
checking if linking against libglut succeeds… yes
checking for freetype-config… /usr/bin/freetype-config
checking freetype include flags… -I/usr/include/freetype2
checking freetype libtool file… -lfreetype -lz
checking for sdl-config… /usr/bin/sdl-config
checking SDL.h usability… yes
checking SDL.h presence… yes
checking for SDL.h… yes
checking IL/il.h usability… yes
checking IL/il.h presence… yes
checking for IL/il.h… yes
configure: WARNING: The DevIL library (libIL.a or libIL.so) cannot be found.
Please set LDFLAGS appropriately or you can specify the location of the DevIL installation using the DEVIL environment variable (e.g. ./configure DEVIL=/home/vandermonde/DevIL)
checking for the S-Lang library… yes
checking if libkerosin will be build… no
configure: error: libkerosin cannot be build without all required libraries.

maybe I should install all libs that wrote in front of them “no”.
"sorry, english is not my native language and I am new to linux.

Please @vandermonde, do put CODE tags around computer text and not what you use now: http://forums.opensuse.org/english/information-new-users/advanced-how-faq-read-only/451526-posting-code-tags-guide.html

And may I add some advice.

We are all fellow openSUSE users that spend some unpaid spare time in trying to help other openSUSE users. That means amongst other things that people are free to read threads and answer to them, or to skip them because they do not have the knowledge or because they are formulated badly. That means, that if you want to draw attention and help, you must offer the maxxiumum amount of information so thatother can help you without having to ask for vary obvious things.
This is not about you knowledge of English, because you are perfectly able to formulate in basic English sentences until now (and when your native language is Dutch, which might be the case seeing your name, there is a Dutch forums here). And people here will try toii understand even broken English. But they can not understand missing information.

You should at least tell which openSUSE level you use. Then, because I think that the product you want to build is not something that is used by many people (else it would have been in a standard repository and thus no need for building), a bit of an explantion about this product would be nice. In short, what is it, where did you find it, in what form. What is the installation documentation (often a README) telling, etc.

We are normal people and not clairvoyant.

On 01/31/2012 11:46 AM, vandermonde wrote:
> I should install all libs that wrote in front of them “no”.

just like to make fish soup you must have fish and other needed things,
to make (compile) software you must have the things (libs) needed…

and, if you make fish soup without fish it won’t make you smile . . .


DD
Read what Distro Watch writes: http://tinyurl.com/SUSEonDW

thank you, but I even don’t know what are stuffs like: q77, f77,…
and if this stuffs are vital why didn’t the process ended up where it was checking them.

This is no answewr to any of the questions I tried to make politely above.

What is this rcssserver3d?
Where did you find it?
What exectly did you find?
Did you download something?
What did you do after that?

rcssserver3d is: robocup 3d soccer simulator. you can find it at: http://dfn.dl.sourceforge.net/project/sserver/rcssserver3D and any other rpm provider site. and I think this part of it’s read me file may be helpful:

The different parts of this package are organized in different
directories as follows:

./app/ Different applications. These applications are
mostly tests of different subsystems of the
simulator. Additionaly, there is
./app/simulator/ The soccer simulator.
./app/ A simple monitor that displays agents connected to
rcssmonitor3d/ the simulator.
./app/agenttest/ A ‘hello world’ agent (does nothing very useful,
kick and run soccer).
./lib/ The main simulator parts as libraries. The
simulator consists of these parts:
./lib/salt/ This library provides a collection of useful
general purpose classes. It contains mostly
math-and system-related functionality, such as a 3D
Vector class, a Matrix class, a file I/O wrapper
and an abstraction for loading/accessing shared
libraries.
./lib/zeitgeist/ The Zeitgeist library provides two major features.
It implements a mechanism to work with class
objects in C++. A class object is just a factory of
class instances. In addition to this mechanism, it
also implements an object hierarchy. This hierarchy
is essentially a virtual file system, where the
‘directories’ and ‘files’ are instances of C++
classes. These two concepts are quite intertwined
with each other, as class objects can also live
inside the object hierarchy. Objects within the
hierarchy are identified with a unique name. On top
of these two features, the Zeitgeist library also
provides three very important ‘built-in’ services.
Each basic service is usually represented by a
‘server’ class in our terminology. An instance of
such a class provides the service to other parts of
the system. The three services built into the
Zeitgeist library are the LogServer, the
FileServer, and the ScriptServer.
./lib/oxygen/ Oxygen is the actual engine which is used for the
simulation. It is implemented on top of the
Zeitgeist framework and provides a multitude of
different services to a client application. It
handles the physics aspect (PhysicsServer), the
geometry aspect (PhysicsServer) and the agent
aspect (AgentAspect, ControlAspect). Another
important part of this library is performing the
world simulation (SceneServer).
./lib/kerosin/ Kerosin handles the visualization aspect
(ImageServer, FontServer, OpenGLServer,
TextureServer, MaterialServer). The classes in the
library also provide basic interfaces for receiving
input in interactive simulations (InputServer) and
for playing sounds (SoundServer). Currently, it is
not used for the simulator.
./plugins/ directory containing plugins to extend the
simulator

I’m using opensuse 12.1 . and I’m not dutch I just like this name (vandermonde).

You not being Dutch I will have some consideration with you :frowning:

I asked five (5) questions. You answered three (3) at the most. It that something that makes me happy? (you do not have to answer this one).

What exectly did you download? Was it rcssserver-15.0.1.tar.gz? When yes, why didn’t you say so. When no, what was it then?

My last question there may be to difficult to answer. I guess you have forgotten. But try to remember where you put that .tar.gz file, What you did then (most probably you unpacked, but tell how!!!). We need information. And as you tell you are new to Linux, we need more information because it is then not obvious you did the correct things.

A presequisite for building software is that you have compliers and the like installed. Go to YaST > Software > Software management; from the Views tab choose Patterns. Now go down the list until you find the Development list. The first down there is Basic developement. Check it in the checkbox left and install by clicking Accept at Low-Right.
This will give you all the compilers and tools like make that you probably need.

I downloaded rcssserver3d-0.6.tar.gz (I think rcssserver-15.0.1.tar.gz is for 2d simulation) to my my “Downloads” folder then I right-clicked on it and selected “extract archive here” choice .
in console I went to its path and then I wrote ./configure

I downloaded rcssserver3d-0.6.tar.gz (I think rcssserver-15.0.1.tar.gz is for 2d simulation) to my my “Downloads” folder then I right-clicked on it and selected “extract archive here” choice .
in console I went to its path and then I wrote ./configure

Did you install the Basic developement pattern in the mean time?
When yes, then repeat starting a terminal emulator and do the cd to the correct directory, an* ls -l *and the ./configure. Then post all of this here (that is starting from the first prompt until the last prompt in one mouse copy/past) between CODE tags.

I forgot to say that I installed many dependencies were needed with yast or downloading rpm file and using the "rpm -i " command.

what is Basic development pattern?

From my post #12 above:

A presequisite for building software is that you have compliers and the like installed. Go to YaST > Software > Software management; from the Views tab choose Patterns. Now go down the list until you find the Development list. The first down there is Basic developement. Check it in the checkbox left and install by clicking Accept at Low-Right.
This will give you all the compilers and tools like make that you probably need.

I hope you read, reread and think about all and everything we post. And then you either do accordingly, or ask questions when you got stuck, or report that you are not willing to do something for whatever reason.

I am not going to repeat myself every three posts or so.

OK now I have installed the base development.
but sorry, I didn’t understand this part of what you said:

an ls -l and the ./configure. Then post all of this here (that is starting from the first prompt until the last prompt in one mouse copy/past) between CODE tags.

You do

cd Dowmloads/directory-where-the-unpacked-stuff-is

as you told you did earlier. Then you do there

ls -l

and then

./configure

Then you grab all the text from the terminal with the mouse to copy/paste this in a post here, but between CODE tgas, as I told you in post #6 more then 4 hours ago.