Info in TUnixSystem::ACLiC: creating shared library /gpfs/csic_users/arodrig/MyProofAnalysis/ProofAnalysisFramework/mymacro_C.so
+++ Starting PROOF-Lite with 2 workers +++
Opening connections to workers: OK (2 workers)
Setting up worker servers: OK (2 workers)
PROOF set to parallel mode (2 workers)
Info in TUnixSystem::ACLiC: creating shared library /gpfs/csic_users/arodrig/.proof/packages/InputParameters/./mymacro_C.so
/usr/lib/crt1.o(.text+0x18): In function _start': : undefined reference tomain’
collect2: ld returned 1 exit status
and just after the code crashed. If I avoid the CompileMacro step the code works fine, but I am not able to use what is in mymacro, and I need before the PROOF session.
We should have probably explained better the use case. We are building a PROOF macro which will set all the information we need for PROOF at the very first lines: Proof server (or prooflite), data files, input parameters, feedback histograms, selector file, etc… After all those initial setting is when (hidden probably in some management class) we would like to start proof. The idea is that the user only edits a few lines of code.
We are using for the input parameters the InputParameters class I think you provided us sometime ago (Ana can confirm where it came from). That is the “macro” we try to load first and then pass it to the proof slaves.
The weird thing for me is that if you load the class and then try to enable it on PROOF it will come with that strange error. I wonder if there is a mechanism to avoid that (either in Setup.C or on the main macro). If you need some test code just let us know.
If not we will have to be a bit more imaginative and find a way to hide all the routine tasks to our users. Thanks for your help!
Yes, I remember the input parameters example and I think more or less what you are trying to do.
The error that you get is strange and I need to investigate it with some CINT expert (I managed
to reproduce it in a very simple case).
However, I believe hat we can have a solution in which you do not need to call CompileMacro before starting PROOF. If you can send some test code I can have a look and propose something.
Any news on a possible workaround this issue? I thin that the use case of someone wanting to fill an object of some kind to be passed onto the PROOF slaves arises pretty soon when you want to do something a bit structured. I remember I could have this working in the far past times