[Rivet] Rivet cannot to be configured with swig

Holger Schulz holger.schulz at durham.ac.uk
Wed Mar 29 15:40:03 BST 2017
Previous message: [Rivet] Rivet cannot to be configured with swig
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Kamuran,

since you are using lxplus anyways, you could just use the central
installation of Rivet2.5.3 from lcg:
e.g. do
source
/cvmfs/sft.cern.ch/lcg/releases/LCG_88/MCGenerators/rivet/2.5.3/x86_64-slc6-gcc62-opt/rivetenv.sh

Cheers,
Holger


On 29/03/17 13:55, Kamuran Dilsiz wrote:
> Dear Frank,
>
> Yes. I used bootstrap script. But, I do not know if it was installed correctly. When did "rivet --list-analyses", it says "The rivet Python module could not be loaded: is your PYTHONPATH set correctly?"
> ________________________________________
> From: Andy Buckley
> Sent: Wednesday, March 29, 2017 2:29 PM
> To: Kamuran Dilsiz; Frank Siegert
> Cc: Rivet
> Subject: Re: [Rivet] Rivet cannot to be configured with swig
>
> You are trying to install to a system directory. You need to provide the
> --prefix argument to Rivet's configure script, as you presumably did for
> installing YODA. Or, as Frank suggested, use the bootstrap script which
> makes all these choices for you.
>
> Andy
>
>
> On 29/03/17 13:17, Kamuran Dilsiz wrote:
>> Hi Andy,
>>
>> Thanks for replying on my e-mail. That solved the problem. But, I encountered another one while doing "make install". The error is like below. Could you please help me fix this?
>>
>> Making install in src
>> make[1]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src'
>> Making install in Core
>> make[2]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Core'
>> Making install in yamlcpp
>> make[3]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Core/yamlcpp'
>> make[4]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Core/yamlcpp'
>> make[4]: Nothing to be done for `install-exec-am'.
>> make[4]: Nothing to be done for `install-data-am'.
>> make[4]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Core/yamlcpp'
>> make[3]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Core/yamlcpp'
>> make[3]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Core'
>> make[4]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Core'
>> make[4]: Nothing to be done for `install-exec-am'.
>> make[4]: Nothing to be done for `install-data-am'.
>> make[4]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Core'
>> make[3]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Core'
>> make[2]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Core'
>> Making install in Tools
>> make[2]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Tools'
>> make[3]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Tools'
>> make[3]: Nothing to be done for `install-exec-am'.
>> make[3]: Nothing to be done for `install-data-am'.
>> make[3]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Tools'
>> make[2]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Tools'
>> Making install in Projections
>> make[2]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Projections'
>> make[3]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Projections'
>> make[3]: Nothing to be done for `install-exec-am'.
>> make[3]: Nothing to be done for `install-data-am'.
>> make[3]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Projections'
>> make[2]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Projections'
>> Making install in Analyses
>> make[2]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Analyses'
>> make  install-am
>> make[3]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Analyses'
>> make[4]: Entering directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Analyses'
>>  /bin/mkdir -p '/usr/local/lib'
>>  /bin/sh ../../libtool   --mode=install /usr/bin/install -c   RivetALICEAnalyses.la RivetATLASAnalyses.la RivetCMSAnalyses.la RivetLHCbAnalyses.la RivetLHCfAnalyses.la RivetTOTEMAnalyses.la RivetCDFAnalyses.la RivetD0Analyses.la RivetHERAAnalyses.la RivetPetraAnalyses.la RivetLEPAnalyses.la RivetRHICAnalyses.la RivetSPSAnalyses.la RivetMiscAnalyses.la RivetMCAnalyses.la '/usr/local/lib'
>> libtool: install: /usr/bin/install -c .libs/RivetALICEAnalyses.so /usr/local/lib/RivetALICEAnalyses.so
>> /usr/bin/install: cannot create regular file `/usr/local/lib/RivetALICEAnalyses.so': Permission denied
>> make[4]: *** [install-libLTLIBRARIES] Error 1
>> make[4]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Analyses'
>> make[3]: *** [install-am] Error 2
>> make[3]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Analyses'
>> make[2]: *** [install] Error 2
>> make[2]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src/Analyses'
>> make[1]: *** [install-recursive] Error 1
>> make[1]: Leaving directory `/afs/cern.ch/user/k/kdilsiz/SHERPA/Rivet-2.5.3/src'
>> make: *** [install-recursive] Error 1
>>
>> ________________________________________
>> From: Andy Buckley
>> Sent: Wednesday, March 29, 2017 12:43 PM
>> To: Kamuran Dilsiz; Frank Siegert
>> Cc: Rivet
>> Subject: Re: [Rivet] Rivet cannot to be configured with swig
>>
>> Hi Karmuran,
>>
>> This message means what it says: to build Rivet you need to be using a
>> fairly modern C++ compiler. If using g++, it will need to be (I think)
>> version 4.8.5 or later.
>>
>> The lxplus6 system compiler is older -- in fact it's very old, and the
>> LHC experiments have *never* used it. The simplest way to get a
>> compliant system may be to use the new lxplus7 system instead. You can
>> also manually set up lxplus6 to use newer build tools like the
>> experiments do, with something like this:
>>
>> . /cvmfs/sft.cern.ch/lcg/releases/LCG_84/gcc/4.9.3/x86_64-slc6/setup.sh
>> .
>> /cvmfs/sft.cern.ch/lcg/releases/LCG_84/Python/2.7.10/x86_64-slc6-gcc49-opt/Python-env.sh
>>
>> (I think that should be sufficient, but in general there are a lot of
>> components to a consistent environment)
>>
>> Hope that helps,
>> Andy
>>
>>
>> On 29/03/17 09:33, Kamuran Dilsiz wrote:
>>> Dear Frank,
>>>
>>> I installed Rivet-2.5.3. But, when configuring this version, I am having the following error which I do not know how to fix.
>>> configure: error: *** A compiler with support for C++11 language features is required.
>>> ________________________________________
>>> From: Frank Siegert
>>> Sent: Wednesday, March 29, 2017 9:44 AM
>>> To: Kamuran Dilsiz
>>> Cc: Rivet
>>> Subject: Re: Rivet cannot to be configured with swig
>>>
>>> Hi Kamuran,
>>> (+ Rivet developer list in CC)
>>>
>>> You should be using the most recent version of Rivet, 2.5.3, instead
>>> of an ancient 1.8.3. This will also solve your swig problem, since
>>> that is not necessary for the recent Rivet versions anymore.
>>>
>>> Last but not least, if you are not familiar with installing programs
>>> on Unix systems you might want to use the rivet bootstrap script,
>>> which will perform the installation automatically for you:
>>> https://rivet.hepforge.org/trac/wiki/GettingStarted
>>>
>>> Cheers,
>>> Frank
>>>
>>>
>>> On 29 March 2017 at 09:23, Kamuran Dilsiz <kamuran.dilsiz at cern.ch> wrote:
>>>> Dear Frank Siegret,
>>>>
>>>> I am using Rivet-1.8.3. I configured it with HepMC and Fastjet, but it also
>>>> require swig. I installed swig into my lxplus account and tried to
>>>> configured Rivet with swig. However, it still gives the following error.
>>>> Could you please help me solve the problem? Thanks in advance.
>>>>
>>>>
>>>> configure: WARNING: cannot find 'swig' program. You should look at
>>>> http://www.swig.org
>>>>
>>>> ./configure: line 18427: test: too many arguments
>>>>
>>>> checking if echo "Error: SWIG is not installed. You should look at
>>>> http://www.swig.org" ; false can make a Python function wrapper... yes
>>>>
>>>> checking if the /usr/bin/g++ compiler accepts the -Wno-format flag... yes
>>>>
>>>> configure: adding -Wno-format to swig compilation test
>>>>
>>>> checking if echo "Error: SWIG is not installed. You should look at
>>>> http://www.swig.org" ; false is compatible with the /usr/bin/g++ compiler...
>>>> no
>>>>
>>>> configure: error: Can't build Python extension since echo "Error: SWIG is
>>>> not installed. You should look at http://www.swig.org" ; false is not
>>>> compatible with /usr/bin/g++. Get a newer SWIG version!
>>>>
>>>>
>>>> Best regards,
>>>> Kamuran
>>>>
>>> _______________________________________________
>>> Rivet mailing list
>>> Rivet at projects.hepforge.org
>>> https://www.hepforge.org/lists/listinfo/rivet
>>>
>>
>> --
>> Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
>> Particle Physics Expt Group, University of Glasgow
>>
>
> --
> Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
> Particle Physics Expt Group, University of Glasgow
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> https://www.hepforge.org/lists/listinfo/rivet
Previous message: [Rivet] Rivet cannot to be configured with swig
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Rivet mailing list