[Rivet] --no-as-needed only exists for ELF linkers

Frank Siegert frank.siegert at cern.ch
Tue Jul 23 15:54:07 BST 2013


While we're at it: for me the yaml-cpp tests failed to build on a
cluster (don't remember exactly why), so I disabled them in the
bootstrap script with the -DYAML_CPP_BUILD_TOOLS=OFF cmake option. If
there are no objections I'd also push this change.

Another issue is the --install-autotools option: It doesn't install
m4, which means that autoconf can't be built if the system m4 is too
old. Again, if there are no objections, I'll add the m4 installation
to --install-autotools.

By the way, in case somebody runs into this as well: I've had an issue
on two completely different clusters now (both possibly SuSE-based
though?) that Rivet wouldn't build with the default libtoolize 2.2.6
because the libtool step simply produced no output:

  make[2]: Entering directory `/.../build/rivet/src/Core'
    CXX    libRivetCore_la-Event.lo
  mv: cannot stat `.deps/libRivetCore_la-Event.Tpo': No such file or directory

Using --install-autotools solved that.

Cheers,
Frank



On 23 July 2013 16:39, Andy Buckley <andy.buckley at cern.ch> wrote:
> Precisely! Please add :-)
>
> On 23/07/13 16:35, James Monk wrote:
>> while we're on the subject of niggly little build snafus, I've noticed that the yaml-cpp lib path probably needs to be added to rivetenv.sh.in.  This is exactly the sort of thing we want to iron out for a 2.0 release, so I guess it's ok to add that to trunk this time!
>>
>> cheers,
>>
>> James
>>
>>
>> On 22 Jul 2013, at 21:54, Andy Buckley wrote:
>>
>>> Just checking up on this... and thanks to hg blame I know it's Hendrik
>>> who added that flag ;-) What was the motivation for it? For all other
>>> flags we check them first via the configure script... do we really
>>> require --no-as-needed in plugin building on Linux?
>>>
>>> Andy
>>>
>>>
>>> On 17/07/13 16:01, James Monk wrote:
>>>> Hi,
>>>>
>>>> The linker flag --no-as-needed has been added to the rivet-buildplugin script recently.  As far as I know, this only exists on Linux, certainly it causes my linker to fail on OS X.
>>>>
>>>> Can we add a check for OS X as already occurs for the shared library flags, and revert to the old behaviour in that case?
>>>>
>>>> cheers,
>>>>
>>>> James
>>>>
>>>> _______________________________________________
>>>> Rivet mailing list
>>>> Rivet at projects.hepforge.org
>>>> http://www.hepforge.org/lists/listinfo/rivet
>>>>
>>>
>>>
>>> --
>>> Dr Andy Buckley, Royal Society University Research Fellow
>>> Particle Physics Expt Group, University of Edinburgh / PH Dept, CERN
>>
>>
>
>
> --
> Dr Andy Buckley, Royal Society University Research Fellow
> Particle Physics Expt Group, University of Edinburgh / PH Dept, CERN
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> http://www.hepforge.org/lists/listinfo/rivet


More information about the Rivet mailing list