Humm

• [^]Re: Humm

  Posté par Nap (page perso, ) le 10/08/2004 à 17:28. (lien). Évalué à 2.

  Salut : voilà ce que donne le configure sur la RH :
  
  [admin@linux-entreprise-server essai]$ ./configure
  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 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 library containing strerror... none required
  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 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 how to run the C preprocessor... gcc -E
  checking for egrep... grep -E
  checking for ANSI C header files... yes
  checking build system type... i686-pc-linux-gnu
  checking host system type... i686-pc-linux-gnu
  checking for a sed that does not truncate output... /bin/sed
  checking for ld used by gcc... /usr/bin/ld
  checking if the linker (/usr/bin/ld) is GNU ld... yes
  checking for /usr/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 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... g77
  checking whether we are using the GNU Fortran 77 compiler... yes
  checking whether g77 accepts -g... yes
  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 static flag works... yes
  checking if gcc supports -fno-rtti -fno-exceptions... yes
  checking for gcc option to produce PIC... -fPIC
  checking if gcc PIC flag -fPIC works... yes
  checking if gcc supports -c -o file.o... yes
  checking whether the gcc linker (/usr/bin/ld) 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 if libtool supports shared libraries... yes
  checking whether to build shared libraries... yes
  checking whether to build static libraries... yes
  configure: creating libtool
  appending configuration tag "CXX" to libtool
  checking for ld used by g++... /usr/bin/ld
  checking if the linker (/usr/bin/ld) is GNU ld... yes
  checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
  checking for g++ option to produce PIC... -fPIC
  checking if g++ PIC flag -fPIC works... yes
  checking if g++ supports -c -o file.o... yes
  checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
  checking dynamic linker characteristics... GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking whether stripping libraries is possible... yes
  appending configuration tag "F77" to libtool
  checking if libtool supports shared libraries... yes
  checking whether to build shared libraries... yes
  checking whether to build static libraries... yes
  checking for g77 option to produce PIC... -fPIC
  checking if g77 PIC flag -fPIC works... yes
  checking if g77 supports -c -o file.o... yes
  checking whether the g77 linker (/usr/bin/ld) supports shared libraries... yes
  checking dynamic linker characteristics... GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking whether stripping libraries is possible... yes
  configure: creating ./config.status
  config.status: creating Makefile
  config.status: creating src/Makefile
  config.status: creating config.h
  config.status: config.h is unchanged
  config.status: executing depfiles commands
  
  François

  • [^]Re: Humm

    Posté par Ayrton () le 10/08/2004 à 23:34. (lien). Évalué à 2.

    Tout semble OK pour le "./configure"
    
    > [admin@linux-entreprise-server essai]$ make
    > cd . && /bin/sh /home/admin/essai/missing --run autoconf
    
    Normalement le programme missing ne doit pas être excécuté sur la machine cible. Fais tourné missing (./missing ou /usr/share/automake-*/missing sur la bécane de développement en premier (ici FC2)).
    
    NB : je ne suis pas un spécialiste de autoconf.