artdaq

I noticed this when trying to run the artdaq demmo and DAQInterface couldn't run its fhicl-dump step because the setup of fhiclcpp was failing.

The problem is that the boost v1_70_0.version directory lists an e19 variant, but that doesn't actually exist in the v1_70_0 version that is installed.

[biery@mu2edaq13 boost]$ hostname
mu2edaq13
[biery@mu2edaq13 boost]$ date
Thu Oct 3 10:15:58 CDT 2019
[biery@mu2edaq13 boost]$ pwd
/cvmfs/fermilab.opensciencegrid.org/products/artdaq/boost
[biery@mu2edaq13 boost]$ ls alF v1_70_0.version/
total 10
drwxrwsr-x 2 cvmfs cvmfs 4096 Oct 2 12:46 ./
drwxrwsr-x 12 cvmfs cvmfs 4096 Oct 2 12:06 ../
-rw-r--r- 1 cvmfs cvmfs 343 Apr 24 10:23 Linux64bit+3.10-2.17_e17_prof
rw-r--r- 1 cvmfs cvmfs 343 Apr 24 10:24 Linux64bit+3.10-2.17_e19_prof
[biery@mu2edaq13 boost]$ ls alF v1_70_0/
total 23
drwxrwsr-x 5 cvmfs cvmfs 4096 Oct 3 03:44 ./
drwxrwsr-x 12 cvmfs cvmfs 4096 Oct 2 12:06 ../
-rw-r--r- 1 cvmfs cvmfs 0 Oct 3 03:44 .cvmfscatalog
drwxr-sr-x 4 cvmfs cvmfs 4096 Apr 24 10:23 Linux64bit+3.10-2.17-e17-prof/
drwxr-sr-x 3 cvmfs cvmfs 4096 Apr 24 10:20 source/
drwxr-sr-x 2 cvmfs cvmfs 4096 Apr 22 11:03 ups/

While we're waiting to get this fixed, the work-around is to change the DAQInterface/.setup_fhiclcpp file to use

• setup "fhiclcpp" "v4_10_00" -q "e17:prof"