You are here: Home » Topic » suse 10.2 64 bit installation

suse 10.2 64 bit installation

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #1645
    gariac
    Guest

    With a bit of hacking and googling, this is the configure line I have come up with:
    ./configure –enable-sqlite3 -enable-=avahi -enable-oggvorbis –enable-flac –enable-musepack –enable-ffmpeg –with-ffmpeg==/usr/include/ffmpeg/ –enable-upnp –with-id3tag=/usr/lib64/libid3tag.so.0.3.0 –prefix=/usr

    I’m not sure why I have to specify the limid3tag location.

    Anyway, the configure doesn’t work; Here is the result


    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 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 for style of include used by make… GNU
    checking dependency style of gcc… gcc3
    checking for bison… bison -y
    checking for flex… flex
    checking for yywrap in -lfl… yes
    checking lex output file root… lex.yy
    checking whether yytext is a pointer… yes
    checking build system type… x86_64-unknown-linux-gnu
    checking host system type… x86_64-unknown-linux-gnu
    checking for pthread_creat in -lc_r… no
    checking for pthread_create in -lpthread… yes
    Host type is x86_64-unknown-linux-gnu
    checking how to run the C preprocessor… /lib/cpp
    configure: error: C preprocessor “/lib/cpp” fails sanity check
    See `config.log’ for more details.


    Assume I’m a newbie regarding linux.

    #12132
    rpedde
    Participant

    @gariac wrote:

    With a bit of hacking and googling, this is the configure line I have come up with:
    ./configure –enable-sqlite3 -enable-=avahi -enable-oggvorbis –enable-flac –enable-musepack –enable-ffmpeg –with-ffmpeg==/usr/include/ffmpeg/ –enable-upnp –with-id3tag=/usr/lib64/libid3tag.so.0.3.0 –prefix=/usr

    I’m not sure why I have to specify the limid3tag location.

    Anyway, the configure doesn’t work; Here is the result


    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 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 for style of include used by make… GNU
    checking dependency style of gcc… gcc3
    checking for bison… bison -y
    checking for flex… flex
    checking for yywrap in -lfl… yes
    checking lex output file root… lex.yy
    checking whether yytext is a pointer… yes
    checking build system type… x86_64-unknown-linux-gnu
    checking host system type… x86_64-unknown-linux-gnu
    checking for pthread_creat in -lc_r… no
    checking for pthread_create in -lpthread… yes
    Host type is x86_64-unknown-linux-gnu
    checking how to run the C preprocessor… /lib/cpp
    configure: error: C preprocessor “/lib/cpp” fails sanity check
    See `config.log’ for more details.


    Assume I’m a newbie regarding linux.

    That actually looks like you don’t have all the packages you need for compiling.

    Not sure what you need on suse, but I’d guess you’d want the packages for gcc, g++, libc-devel, libid3tag-devel (and all the -devel packages for all the stuff you configured for — libavahi-client-devel, libogg-devel, libvorbis-devel, taglib-devel, etc)

    Also, you can check the config.log, and it will show you the command that failed, and what the error was. that sometimes helps determine what package you might be missing, or what files it can’t find that it expects to find.

    — Ron

Viewing 2 posts - 1 through 2 (of 2 total)
  • The forum ‘Setup Issues’ is closed to new topics and replies.