[Rivet] undefined MAIN?

[Andy Buckley]

Hmm, where on earth are those coming from? There shouldn't be *any* main 
function in a library! From my local build of Rivet HEAD:

$ nm src/.libs/libRivet.so | grep MAIN__
$ nm src/.libs/libRivet.so | grep main
00000000000a4c90 T _ZNK5Rivet7WFinder19remainingFinalStateEv
00000000000a7bd0 T _ZNK5Rivet7ZFinder19remainingFinalStateEv

So it's something about how it's been built on lxplus, I think.

Andy


James Monk wrote:
> yup, checked that already:
> 
> MAIN__ U
> ...later
> main T 00000000000dd8f0 000000000000004b
> 
> James
> 
> On 18 Dec 2009, at 20:05, Andy Buckley wrote:
> 
>> James Monk wrote:
>>> Hi,
>>> I'm trying to get the Rivet svn head version running privately in  
>>> Athena (to access the UA5 analyses).  When Athena links it there is 
>>> an  error of a missing main:
>>> ERROR: 
>>> /home/jmonk/Genser/rivet//r2198/slc4_ia32_gcc34/lib/libRivet.so. 5: 
>>> undefined symbol: MAIN__
>>> This stumps me a bit really as Rivet shouldn't itself have any  
>>> references to main, and neither should anything it links against - 
>>> or  has that changed?
>>
>> That's weird -- usually those dummy main symbols only appear from 
>> Fortran code. Do you actually see a "U" symbol for "MAIN__" when you use
>>
>> nm /home/jmonk/Genser/rivet//r2198/slc4_ia32_gcc34/lib/libRivet.so | 
>> grep "MAIN__"
>>
>> ?
>>
>> Andy
>>
>> -- 
>> Dr Andy Buckley
>> SUPA Advanced Research Fellow
>> Particle Physics Experiment Group, University of Edinburgh
> 
> 


-- 
Dr Andy Buckley
SUPA Advanced Research Fellow
Particle Physics Experiment Group, University of Edinburgh