1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: ADEiger for EIGER2 |
From: | John Dobbins via Tech-talk <tech-talk at aps.anl.gov> |
To: | "Perez Juarez, Emilio (DLSLtd,RAL,LSCI)" <emilio.perez-juarez at diamond.ac.uk>, Mark Rivers <rivers at cars.uchicago.edu> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Tue, 24 Nov 2020 19:27:41 +0000 |
I get a build error related to the lz4 library (see below) I poked around and I am confused about where lz4 gets configured. I am using base-7.0.3 , areaDetector-master (is that a problem?)
On out SL7 systems
>locate lz4
/usr/lib/liblz4.so.1
/usr/lib/liblz4.so.1.7.5
/usr/lib64/liblz4.so.1
/usr/lib64/liblz4.so.1.7.5
but I also thought bitshhuffle from ADSupport provides LZ4.
Finally, I see that
/usr/bin/g++ -o libeigerDetector.so -shared -fPIC -Wl,-hlibeigerDetector.so -L/nfs/chess/epics/det/support/areaDetector/ADEiger/lib/linux-x86_64 -L/nfs/chess/epics/det/base-7.0.3/lib/linux-x86_64 -L/nfs/chess/epics/det/support/areaDetector/ADCore/lib/linux-x86_64
-L/nfs/chess/epics/det/support/areaDetector/ADSupport/lib/linux-x86_64 -L/nfs/chess/epics/det/support/asyn-R4-40-1/lib/linux-x86_64 -L/nfs/opt/zmq-4.3.1-23.3.x86_64/lib -Wl,-rpath,/nfs/chess/epics/det/support/areaDetector/ADEiger/lib/linux-x86_64 -Wl,-rpath,/nfs/chess/epics/det/base-7.0.3/lib/linux-x86_64
-Wl,-rpath,/nfs/chess/epics/det/support/areaDetector/ADCore/lib/linux-x86_64 -Wl,-rpath,/nfs/chess/epics/det/support/areaDetector/ADSupport/lib/linux-x86_64 -Wl,-rpath,/nfs/chess/epics/det/support/asyn-R4-40-1/lib/linux-x86_64 -Wl,-rpath,/nfs/opt/zmq-4.3.1-23.3.x86_64/lib
-rdynamic -m64 eigerDetector.o restApi.o streamApi.o eigerParam.o -lzmq -lADBase -lasyn -lnetCDF -lMagick++ -lcoders -lMagick -ljbig -ljp2 -lbzlib -lpng -lwebp -llcms -lttf -lwmf -lfilters -ltiff -lxml2 -lNeXus -lhdf5 -lhdf5_hl -lbitshuffle
-lblosc -lszip -lzlib -ljpeg -ldbRecStd -ldbCore -lca -lCom -llz4 -lbitshuffle -lhdf5_hl -lX11 -lXext -lpthread -lreadline -lm -lrt -ldl -lgcc
/usr/bin/ld: cannot find -llz4
collect2: error: ld returned 1 exit status
From: Perez Juarez, Emilio (DLSLtd,RAL,LSCI) <emilio.perez-juarez at diamond.ac.uk>
Sent: Tuesday, November 24, 2020 11:47 AM To: John Dobbins <john.dobbins at cornell.edu>; Mark Rivers <rivers at cars.uchicago.edu> Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: Re: ADEiger for EIGER2
Hi, here's another approach:
$ git clone https://github.com/areaDetector/ADEiger
$ cd ADEiger/
$ git fetch origin pull/30/head:pr-branch
$ git checkout pr-branch
I think this way you get the result of merging to the target branch
Kind Regards,
Emilio
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
Sent: 24 November 2020 16:33 To: John Dobbins <john.dobbins at cornell.edu> Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: Re: ADEiger for EIGER2 Hi John,
You can clone the repository issuing that pull request and then checkout that branch: git clone https://github.com/dls-controls/ADEiger/ cd ADEiger git checkout 1.8 Mark ________________________________ From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of John Dobbins via Tech-talk <tech-talk at aps.anl.gov> Sent: Tuesday, November 24, 2020 10:16 AM To: tech-talk at aps.anl.gov Subject: ADEiger for EIGER2 All, I have a new EIGER 2 detector. I understand that this https://github.com/areaDetector/ADEiger/pull/30 is the appropriate ADEiger for an EIGER 2. True? Can someone tell me how to clone this pull? Thanks, John Dobbins Research Support Specialist Cornell High Energy Synchrotron Source Cornell University www.chess.cornell.edu<http://www.chess.cornell.edu>
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised
recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. |