Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Troubleshooting MC | ||||||||
Line: 18 to 18 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
Code compilation |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Troubleshooting MC | ||||||||
Changed: | ||||||||
< < | This page lists the most common problems encoutered with the NA62 MC code, along with more or less general solutions. | |||||||
> > | This page lists the most common problems encoutered with the NA62 MC code and the whole grid production setup, along with our solutions. | |||||||
Line: 15 to 15 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Code compilation |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Troubleshooting MC | ||||||||
Line: 32 to 32 | ||||||||
$(FC) -shared -Wl,-soname,$(CMCLIBNAME) -o $(CMCLIB) $^
This way the .so is linked w/o the full path, which ensures portability of the executable. Same trick in Beam/GNUmakefile , but variable names BEAMLIBNAME and BEAMLIB .
\ No newline at end of file | ||||||||
Added: | ||||||||
> > |
Access permissionsMany errors came from read/write access permissions either for the local software area on sites, or for storage paths on various SEs. Using two certificates - one for jobs submission (and writing to the local storage) and the other for output replication to RAL and CERN complicates things somewhat. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Troubleshooting MC | ||||||||
Line: 15 to 15 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Code compilation |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Troubleshooting MC | ||||||||
Line: 15 to 15 | ||||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Code compilation |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Troubleshooting MC | ||||||||
Line: 6 to 6 | ||||||||
Added: | ||||||||
> > | GGUS ticketsSome of the problems encountered are available as GGUS tickets:
| |||||||
Code compilationShared object portability issue. InGenerator/GNUmakefile , define a new variable CMCLIBNAME , just above the existing CMCLIB definition: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Troubleshooting MC | ||||||||
Line: 8 to 8 | ||||||||
Code compilation | ||||||||
Changed: | ||||||||
< < | Shared object portability issue. In Generator/GNUmakefile and Beam/GNUmakefile , define a new variable CMCLIBNAME , just above the existing CMCLIB definition: | |||||||
> > | Shared object portability issue. In Generator/GNUmakefile , define a new variable CMCLIBNAME , just above the existing CMCLIB definition: | |||||||
CMCLIBNAME := libcmc.so CMCLIB := $(CMCDIR)/libcmc.so | ||||||||
Line: 20 to 20 | ||||||||
$(CMCLIB): $(OBJF) $(OBJC) $(COMMONOBJ) $(OBJCC) $(FC) -shared -Wl,-soname,$(CMCLIBNAME) -o $(CMCLIB) $^ | ||||||||
Changed: | ||||||||
< < | This way the .so is linked w/o the full path, which ensures portability of the executable. | |||||||
> > | This way the .so is linked w/o the full path, which ensures portability of the executable. Same trick in Beam/GNUmakefile , but variable names BEAMLIBNAME and BEAMLIB . | |||||||
\ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
Troubleshooting MCThis page lists the most common problems encoutered with the NA62 MC code, along with more or less general solutions.Code compilationShared object portability issue. InGenerator/GNUmakefile and Beam/GNUmakefile , define a new variable CMCLIBNAME , just above the existing CMCLIB definition:
CMCLIBNAME := libcmc.so CMCLIB := $(CMCDIR)/libcmc.soand then the target: Generator: $(CMCLIB) $(CMCLIB): $(OBJF) $(OBJC) $(COMMONOBJ) $(OBJCC) $(FC) -shared -Wl,-soname,$(CMCLIBNAME) -o $(CMCLIB) $^This way the .so is linked w/o the full path, which ensures portability of the executable. |