rivet is hosted by Hepforge, IPPP Durham
close Warning: Can't synchronize with repository "(default)" (Repository path '/hepforge/hg/rivet/public/rivet' does not exist.). Look in the Trac log for more information.

Opened 14 years ago

Closed 14 years ago

#42 closed defect (invalid)

rivet installation fails at CERN

Reported by: Lars Sonnenschein Owned by: all
Priority: blocker Milestone:
Component: General Version:
Keywords: Installation problems Cc:

Description

Meanwhile I have been able to get the configure script finnishing without any problems when I replace in configure.ac:

AC_CEDAR_LIBRARYANDHEADERS([KtJet], , , [AC_MSG_ERROR(library is required?)]) dnl AC_CEDAR_HEADERS([KtJet], , , [AC_MSG_ERROR(headers are required)])

with:

AC_CEDAR_LIBRARY([KtEvent?], , , [AC_MSG_ERROR(library is required?)]) AC_CEDAR_HEADERS([KtJet], , , [AC_MSG_ERROR(headers are required)])

as seen in the configure.ac script of my Durham installation.

The next error I get during execution of make is the following one:

make[2]: Entering directory `/build/sonne/cedar/rivet_anonymous/src' /bin/sh ../libtool --mode=link --tag=CXX g++ -ansi -pedantic -Wall -g -O2 -o libRivet.la -rpath /build/sonne/local/lib -version-info 1:0:0 -export-dynamic -L -R -L -R -L/build/sonne/local/lib -R/build/sonne/local/lib -L/build/sonne/local/lib -R/build/sonne/local/lib -L/build/sonne/local/lib -R/build/sonne/local/lib -L -R RivetHandler.lo RivetInfo.lo Analysis/libRivetAnalysis.la Projections/libRivetProjections.la Tools/libRivetTools.la -ldl -llog4cpp -l -l -lHepPID -lHepPDT -l libtool: link: only absolute run-paths are allowed make[2]: * [libRivet.la] Error 1 make[2]: Leaving directory `/build/sonne/cedar/rivet_anonymous/src' make[1]: * [all-recursive] Error 1 make[1]: Leaving directory `/build/sonne/cedar/rivet_anonymous/src' make: * [all-recursive] Error 1

What does that mean?

Change History (2)

comment:1 Changed 14 years ago by Andy Buckley

Changing those autoconf macros won't work: instead, make a symlink from libKtJet.so which points at libKtEvent.so (if you can't upgrade KtJet to the head version)

The absolute path problem is due to the -L and -R switches with no arguments in the build command. The null arguments are because of other references to KTJET rather than KTEVENT in the build files, which aren't getting expanded correctly because of your changes to configure.ac.

comment:2 Changed 14 years ago by Andy Buckley

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.