make+autotools in RH8

From: Flemming Videbaek (videbaek@rcf.rhic.bnl.gov)
Date: Mon Sep 15 2003 - 15:36:21 EDT

  • Next message: Hironori Ito: "[Fwd: [Rhic-rcf-l] update on OS upgrade (BRAHMS & PHOBOS)]"
     
    
    Some question in regards to the new setup for RH8.0 etc.
    
    This needs a real expert for autotools - and I am not one; 
    It may be in the manual but if anyone knows this let us attempt to fix these
    # issue described below.
    
    
    
    
    
    II brop ******************
    ____
    
    The combinations of autotools now produce the following warnings for each
    single module compiled
    
    
    source='BrBaseMonitor.cxx' object='BrBaseMonitor.lo' libtool=yes \
    depfile='.deps/BrBaseMonitor.Plo' tmpdepfile='.deps/BrBaseMonitor.TPlo' \
    depmode=gcc3 /bin/sh ../../config/depcomp \
    /bin/sh ../../libtool --mode=compile g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"brop\" -DVERSION=\"1.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1  -I. -I.  -I. -D_REENTRANT -I/afs/rhic.bnl.gov/opt/brahms/new/include/root -DPACKAGE_NAME= -DPACKAGE_TARNAME= -DPACKAGE_VERSION= -DPACKAGE_STRING= -DPACKAGE_BUGREPORT= -DONL_unix=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
    -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -I/home2/home/videbaek/include/brat   -g -O2 -c -o BrBaseMonitor.lo `test -f 'BrBaseMonitor.cxx' || echo './'`BrBaseMonitor.cxx
    g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"brop\" -DVERSION=\"1.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -I. -I. -I. -D_REENTRANT -I/afs/rhic.bnl.gov/opt/brahms/new/include/root -DPACKAGE_NAME= -DPACKAGE_TARNAME= -DPACKAGE_VERSION= -DPACKAGE_STRING= -DPACKAGE_BUGREPORT= -DONL_unix=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -I/home2/home/videbaek/include/brat -g -O2 -c BrBaseMonitor.cxx -MT BrBaseMonitor.lo -MD -MP -MF .deps/BrBaseMonitor.TPlo  -fPIC -DPIC -o BrBaseMonitor.lo
    <command line>:1:1: warning: "PACKAGE_NAME" redefined
    <command line>:1:1: warning: this is the location of the previous definition
    <command line>:1:1: warning: "PACKAGE_TARNAME" redefined
    <command line>:1:1: warning: this is the location of the previous definition
    <command line>:1:1: warning: "PACKAGE_VERSION" redefined
    <command line>:1:1: warning: this is the location of the previous definition
    <command line>:1:1: warning: "PACKAGE_STRING" redefined
    <command line>:1:1: warning: this is the location of the previous definition
    <command line>:1:1: warning: "PACKAGE_BUGREPORT" redefined
    <command line>:1:1: warning: this is the location of the previous definition
     
    
    Some names seems in fact blank. Where are these supposed to be set.
    
    III ------------------------------
    
    make -j2
    
    As we all know compiling Brat in particular takes long time; Why can't
    the Makesystem that we build on top of autotools be run with make -j2 i.e. utilizing the dual processors. It starts up but seems always to run into trouble
    likely when same needed in one brahnch are being modified by another ??
    
    Could this be used at the lowest level i.e. for compilation step only?
    
    
    I autogen************  (minor issue)
    ----------
    
    The default autogen has some checks as described. Is this still
    the proper one i.e. this is for C and has no relavance for our C++ stuff?
    
    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
    
    
    ------------------------------------------------------
    Flemming Videbaek
    Physics Department
    Brookhaven National Laboratory
    
    tlf: 631-344-4106
    fax 631-344-1334
    e-mail: videbaek@bnl.gov
    
    ------------------------------------------------------
    Flemming Videbaek
    Physics Department
    Brookhaven National Laboratory
    
    tlf: 631-344-4106
    fax 631-344-1334
    e-mail: videbaek@bnl.gov
    


    This archive was generated by hypermail 2.1.5 : Mon Sep 15 2003 - 15:35:06 EDT