[Rivet] ISSUE Installing RIVET on LXPLUS

Holger Schulz holger.schulz at durham.ac.uk
Tue Jan 2 15:24:46 GMT 2018


Hi Michelle,

that's great news :)

Concerning the environment variables, you can either just always source
the rivetenv.sh
script that comes with the bootstrap script or paste the contents of
that file
into your .bashrc to make those changes permanent, entirely up to you.
I personally prefer just sourcing rivetenv.sh any time I want to use it.
That's
especially handy if you are working with more than one version of the
program.

Cheers,
Holger



On 02/01/18 09:08, MICHELE GROSSI wrote:
> Hi Holger,
> thank you for the quick answer.
> Yes, running the non-lcg version of the script it works well!
>
> Last question, in the final part of the installation it is said: *You
> may wish to add the environment variable settings to your ~/.bashrc
> shell config file, so that Rivet will work without needing any special
> session setup.
> *
> Which are now the environment variable setting that I should add to my
> profile?
>
> Thank again,
> Michele*
> *
>
> 2018-01-02 15:39 GMT+01:00 Holger Schulz <holger.schulz at durham.ac.uk
> <mailto:holger.schulz at durham.ac.uk>>:
>
>     Hi Michele,
>
>     can you check whether the same thing happens with the non-lcg
>     version of the
>     bootstrap script, too?
>
>     Thanks,
>     Holger
>
>
>     On 02/01/18 08:31, MICHELE GROSSI wrote:
>>     Deat RIVET Team,
>>     I am following the instruction to setup and install Rivet on
>>     lxplus but I got error.
>>     May I ask your support,
>>     Thank you
>>     Michele
>>
>>     In the following the output of:
>>
>>     mgrossi at lxplus068 mgrossi]$ ./rivet-bootstrap-lcg
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     accepts the -std=c++11 flag: hurrah! Continuing installation...
>>
>>     Running Rivet bootstrap script with LCG HepMC, FastJet, and GSL
>>     Building Rivet 2.5.4, YODA 1.6.7
>>
>>     Building YODA
>>     --2018-01-02 15:02:52-- 
>>     http://www.hepforge.org/archive/yoda/YODA-1.6.7.tar.gz
>>     <http://www.hepforge.org/archive/yoda/YODA-1.6.7.tar.gz>
>>     Resolving www.hepforge.org <http://www.hepforge.org>...
>>     129.234.186.115
>>     Connecting to www.hepforge.org
>>     <http://www.hepforge.org>|129.234.186.115|:80... connected.
>>     HTTP request sent, awaiting response... 301 Moved Permanently
>>     Location: https://www.hepforge.org/archive/yoda/YODA-1.6.7.tar.gz
>>     <https://www.hepforge.org/archive/yoda/YODA-1.6.7.tar.gz> [following]
>>     --2018-01-02 15:02:52-- 
>>     https://www.hepforge.org/archive/yoda/YODA-1.6.7.tar.gz
>>     <https://www.hepforge.org/archive/yoda/YODA-1.6.7.tar.gz>
>>     Connecting to www.hepforge.org
>>     <http://www.hepforge.org>|129.234.186.115|:443... connected.
>>     HTTP request sent, awaiting response... 200 OK
>>     Length: 1097370 (1.0M) [application/x-gzip]
>>     Saving to: “STDOUT”
>>
>>     100%[==========================================================>]
>>     1,097,370   1.45M/s   in 0.7s
>>
>>     2018-01-02 15:02:53 (1.45 MB/s) - written to stdout [1097370/1097370]
>>
>>     checking for a BSD-compatible install... /usr/bin/install -c
>>     checking whether build environment is sane... yes
>>     checking for a thread-safe mkdir -p... /bin/mkdir -p
>>     checking for gawk... gawk
>>     checking whether make sets $(MAKE)... yes
>>     checking whether make supports nested variables... yes
>>     checking whether make supports nested variables... (cached) yes
>>     checking for style of include used by make... GNU
>>     checking for gcc...
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     checking whether the C compiler works... yes
>>     checking for C compiler default output file name... a.out
>>     checking for suffix of executables...
>>     checking whether we are cross compiling... no
>>     checking for suffix of object files... o
>>     checking whether we are using the GNU C compiler... yes
>>     checking whether
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     accepts -g... yes
>>     checking for
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     option to accept ISO C89... none needed
>>     checking whether
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     understands -c and -o together... yes
>>     checking dependency style of
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc.
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc.>..
>>     gcc3
>>     checking for ar... ar
>>     checking the archiver (ar) interface... ar
>>     checking for sw_vers... no
>>     checking whether we are using the GNU C++ compiler... yes
>>     checking whether
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     accepts -g... yes
>>     checking dependency style of
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++.
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++.>..
>>     gcc3
>>     checking whether
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     supports C++11 features by default... no
>>     checking whether
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     supports C++11 features with -std=c++11... yes
>>     checking whether ln -s works... yes
>>     checking build system type... x86_64-unknown-linux-gnu
>>     checking host system type... x86_64-unknown-linux-gnu
>>     checking how to print strings... printf
>>     checking for a sed that does not truncate output... /bin/sed
>>     checking for grep that handles long lines and -e... /bin/grep
>>     checking for egrep... /bin/grep -E
>>     checking for fgrep... /bin/grep -F
>>     checking for ld used by
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc.
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc.>..
>>     /usr/bin/ld
>>     checking if the linker (/usr/bin/ld) is GNU ld... yes
>>     checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
>>     checking the name lister (/usr/bin/nm -B) interface... BSD nm
>>     checking the maximum length of command line arguments... 1966080
>>     checking whether the shell understands some XSI constructs... yes
>>     checking whether the shell understands "+="... yes
>>     checking how to convert x86_64-unknown-linux-gnu file names to
>>     x86_64-unknown-linux-gnu format... func_convert_file_noop
>>     checking how to convert x86_64-unknown-linux-gnu file names to
>>     toolchain format... func_convert_file_noop
>>     checking for /usr/bin/ld option to reload object files... -r
>>     checking for objdump... objdump
>>     checking how to recognize dependent libraries... pass_all
>>     checking for dlltool... no
>>     checking how to associate runtime and link libraries... printf %s\n
>>     checking for archiver @FILE support... @
>>     checking for strip... strip
>>     checking for ranlib... ranlib
>>     checking command to parse /usr/bin/nm -B output from
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     object... ok
>>     checking for sysroot... no
>>     checking for mt... no
>>     checking if : is a manifest tool... no
>>     checking how to run the C preprocessor...
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/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 for dlfcn.h... yes
>>     checking for objdir... .libs
>>     checking if
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     supports -fno-rtti -fno-exceptions... no
>>     checking for
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     option to produce PIC... -fPIC -DPIC
>>     checking if
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     PIC flag -fPIC -DPIC works... yes
>>     checking if
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     static flag -static works... yes
>>     checking if
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     supports -c -o file.o... yes
>>     checking if
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     supports -c -o file.o... (cached) yes
>>     checking whether the
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/gcc>
>>     linker (/usr/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 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... no
>>     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... no
>>     checking how to run the C++ preprocessor...
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 -E
>>     checking for ld used by
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11... /usr/bin/ld -m elf_x86_64
>>     checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
>>     checking whether the
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 linker (/usr/bin/ld -m elf_x86_64) supports shared
>>     libraries... yes
>>     checking for
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 option to produce PIC... -fPIC -DPIC
>>     checking if
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 PIC flag -fPIC -DPIC works... yes
>>     checking if
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 static flag -static works... yes
>>     checking if
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 supports -c -o file.o... yes
>>     checking if
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 supports -c -o file.o... (cached) yes
>>     checking whether the
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 linker (/usr/bin/ld -m elf_x86_64) supports shared
>>     libraries... yes
>>     checking dynamic linker characteristics... (cached) GNU/Linux ld.so
>>     checking how to hardcode library paths into programs... immediate
>>     checking if the
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 compiler accepts the -pedantic flag... yes
>>     checking if the
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 compiler accepts the -Wall flag... yes
>>     checking for root-config... /usr/bin/root-config
>>     checking ROOT version... 5.34/36 (5,34,36)
>>     configure: Building extra ROOT compatibility tools
>>     checking for python...
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/Python/2.7.10/x86_64-slc6-gcc49-opt/bin/python
>>     <http://sft.cern.ch/lcg/releases/LCG_85/Python/2.7.10/x86_64-slc6-gcc49-opt/bin/python>
>>     checking for a version of Python >= '2.1.0'... yes
>>     checking for a version of Python >= '2.6'... yes
>>     checking for the distutils Python package... yes
>>     checking for Python include path...
>>     -I/cvmfs/sft.cern.ch/lcg/releases/LCG_85/Python/2.7.10/x86_64-slc6-gcc49-opt/include/python2.7
>>     <http://sft.cern.ch/lcg/releases/LCG_85/Python/2.7.10/x86_64-slc6-gcc49-opt/include/python2.7>
>>     checking for Python library path...
>>     -L/cvmfs/sft.cern.ch/lcg/releases/LCG_85/Python/2.7.10/x86_64-slc6-gcc49-opt/lib
>>     <http://sft.cern.ch/lcg/releases/LCG_85/Python/2.7.10/x86_64-slc6-gcc49-opt/lib>
>>     -lpython2.7
>>     checking for Python site-packages path...
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/Python/2.7.10/x86_64-slc6-gcc49-opt/lib/python2.7/site-packages
>>     <http://sft.cern.ch/lcg/releases/LCG_85/Python/2.7.10/x86_64-slc6-gcc49-opt/lib/python2.7/site-packages>
>>     checking python extra libraries... -lpthread -ldl  -lutil -lm
>>     checking python extra linking flags...
>>     checking consistency of all components of python development
>>     environment... yes
>>     checking for python version... 2.7
>>     checking for python platform... linux2
>>     checking for python script directory...
>>     ${prefix}/lib/python2.7/site-packages
>>     checking for python extension module directory...
>>     ${exec_prefix}/lib/python2.7/site-packages
>>     checking for Cython >= 0.23.5... no
>>     checking for pyext/yoda/core.cpp... yes
>>     checking if the
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 compiler accepts the -Wno-unused-but-set-variable
>>     flag... yes
>>     checking if the
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 compiler accepts the -Wno-sign-compare flag... yes
>>     checking if the
>>     /cvmfs/sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++
>>     <http://sft.cern.ch/lcg/releases/LCG_85/gcc/4.9.3/x86_64-slc6/bin/g++>
>>     -std=c++11 compiler accepts the -Wno-strict-prototypes flag... no
>>     configure: All Python build checks successful: 'yoda' Python
>>     extension will be built
>>     checking for doxygen... /usr/bin/doxygen
>>     checking that generated files are newer than configure... done
>>     configure: creating ./config.status
>>     config.status: creating Makefile
>>     config.status: creating Doxyfile
>>     config.status: creating include/Makefile
>>     config.status: creating include/YODA/Makefile
>>     config.status: creating src/Makefile
>>     config.status: creating src/tinyxml/Makefile
>>     config.status: creating tests/Makefile
>>     config.status: creating pyext/Makefile
>>     config.status: creating pyext/setup.py
>>     config.status: creating pyext/yoda/Makefile
>>     config.status: creating bin/Makefile
>>     config.status: creating bin/yoda-config
>>     config.status: creating yodaenv.sh
>>     config.status: creating yoda.pc
>>     config.status: creating include/YODA/Config/DummyConfig.h
>>     config.status: creating include/YODA/Config/YodaConfig.h
>>     config.status: include/YODA/Config/YodaConfig.h is unchanged
>>     config.status: creating include/YODA/Config/BuildConfig.h
>>     config.status: include/YODA/Config/BuildConfig.h is unchanged
>>     config.status: executing depfiles commands
>>     config.status: executing libtool commands
>>
>>     ************************************************************
>>     YODA CONFIGURED!
>>
>>     Now build and install (to the
>>     /afs/cern.ch/work/m/mgrossi/RIVET/local
>>     <http://cern.ch/work/m/mgrossi/RIVET/local> tree) with e.g.
>>     make -j2 && make -j2 install
>>     ************************************************************
>>     Making all in src
>>     make[1]: Entering directory
>>     `/afs/cern.ch/work/m/mgrossi/RIVET/YODA-1.6.7/src
>>     <http://cern.ch/work/m/mgrossi/RIVET/YODA-1.6.7/src>'
>>     Making all in tinyxml
>>     make[2]: Entering directory
>>     `/afs/cern.ch/work/m/mgrossi/RIVET/YODA-1.6.7/src/tinyxml
>>     <http://cern.ch/work/m/mgrossi/RIVET/YODA-1.6.7/src/tinyxml>'
>>       CXX      libtinyxml_la-tinyxmlerror.lo
>>       CXX      libtinyxml_la-tinystr.lo
>>       CXX      libtinyxml_la-tinyxml.lo
>>     g++: internal compiler error: Segmentation fault (program cc1plus)
>>     0x409edc execute
>>         ../../gcc-4.9.3/gcc/gcc.c:2854
>>     0x40a2a4 do_spec_1
>>         ../../gcc-4.9.3/gcc/gcc.c:4658
>>     0x40cb66 process_brace_body
>>         ../../gcc-4.9.3/gcc/gcc.c:5941
>>     0x40cb66 handle_braces
>>         ../../gcc-4.9.3/gcc/gcc.c:5855
>>     0x40b119 do_spec_1
>>         ../../gcc-4.9.3/gcc/gcc.c:5312
>>     0x40cb66 process_brace_body
>>         ../../gcc-4.9.3/gcc/gcc.c:5941
>>     0x40cb66 handle_braces
>>         ../../gcc-4.9.3/gcc/gcc.c:5855
>>     0x40b119 do_spec_1
>>         ../../gcc-4.9.3/gcc/gcc.c:5312
>>     0x40ae83 do_spec_1
>>         ../../gcc-4.9.3/gcc/gcc.c:5427
>>     0x40cb66 process_brace_body
>>         ../../gcc-4.9.3/gcc/gcc.c:5941
>>     0x40cb66 handle_braces
>>         ../../gcc-4.9.3/gcc/gcc.c:5855
>>     0x40b119 do_spec_1
>>         ../../gcc-4.9.3/gcc/gcc.c:5312
>>     0x40cb66 process_brace_body
>>         ../../gcc-4.9.3/gcc/gcc.c:5941
>>     0x40cb66 handle_braces
>>         ../../gcc-4.9.3/gcc/gcc.c:5855
>>     0x40b119 do_spec_1
>>         ../../gcc-4.9.3/gcc/gcc.c:5312
>>     0x40cb66 process_brace_body
>>         ../../gcc-4.9.3/gcc/gcc.c:5941
>>     0x40cb66 handle_braces
>>         ../../gcc-4.9.3/gcc/gcc.c:5855
>>     0x40b119 do_spec_1
>>         ../../gcc-4.9.3/gcc/gcc.c:5312
>>     0x40cb66 process_brace_body
>>         ../../gcc-4.9.3/gcc/gcc.c:5941
>>     0x40cb66 handle_braces
>>         ../../gcc-4.9.3/gcc/gcc.c:5855
>>     Please submit a full bug report,
>>     with preprocessed source if appropriate.
>>     Please include the complete backtrace with any bug report.
>>     See <http://gcc.gnu.org/bugs.html> for instructions.
>>     make[2]: *** [libtinyxml_la-tinystr.lo] Error 1
>>     make[2]: *** Waiting for unfinished jobs....
>>     make[2]: Leaving directory
>>     `/afs/cern.ch/work/m/mgrossi/RIVET/YODA-1.6.7/src/tinyxml
>>     <http://cern.ch/work/m/mgrossi/RIVET/YODA-1.6.7/src/tinyxml>'
>>     make[1]: *** [all-recursive] Error 1
>>     make[1]: Leaving directory
>>     `/afs/cern.ch/work/m/mgrossi/RIVET/YODA-1.6.7/src
>>     <http://cern.ch/work/m/mgrossi/RIVET/YODA-1.6.7/src>'
>>     make: *** [all-recursive] Error 1
>>     [mgrossi at lxplus068 RIVET]$ gcc --v
>>     gcc: error: unrecognized command line option ‘--v’
>>     gcc: fatal error: no input files
>>     compilation terminated.
>>     [mgrossi at lxplus068 RIVET]$ gcc -version
>>     gcc: error: unrecognized command line option ‘-version’
>>     gcc: fatal error: no input files
>>     compilation terminated.
>>
>>     HERE the gcc version
>>     [mgrossi at lxplus068 RIVET]$ gcc --version
>>     gcc (GCC) 4.9.3
>>     Copyright (C) 2015 Free Software Foundation, Inc.
>>     This is free software; see the source for copying conditions. 
>>     There is NO
>>     warranty; not even for MERCHANTABILITY or FITNESS FOR A
>>     PARTICULAR PURPOSE.
>>
>>
>>     _______________________________________________
>>     Rivet mailing list
>>     Rivet at projects.hepforge.org <mailto:Rivet at projects.hepforge.org>
>>     https://www.hepforge.org/lists/listinfo/rivet
>>     <https://www.hepforge.org/lists/listinfo/rivet>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20180102/293eef68/attachment.html>


More information about the Rivet mailing list