Page 1 of 3 123 LastLast
Results 1 to 10 of 27

Thread: GL/gl.h ???

  1. #1

    Default 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?

  2. #2

    Default Re: GL/gl.h ???

    Quote Originally Posted by vandermonde View Post
    (...)
    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

  3. #3

    Default Re: GL/gl.h ???

    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.

  4. #4
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: GL/gl.h ???

    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

  5. #5

    Default Re: GL/gl.h ???

    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.

  6. #6
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,721

    Default Re: GL/gl.h ???

    Please @vandermonde, do put CODE tags around computer text and not what you use now: http://forums.opensuse.org/english/i...ags-guide.html
    Henk van Velden

  7. #7
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: GL/gl.h ???

    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

  8. #8
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,721

    Default Re: GL/gl.h ???

    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.
    Henk van Velden

  9. #9

    Default Re: GL/gl.h ???

    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.

  10. #10
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,721

    Default Re: GL/gl.h ???

    Quote Originally Posted by vandermonde View Post
    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?
    Henk van Velden

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •