<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:14pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Dear Hans,</p>
<p><br>
</p>
<p>thank you very much!</p>
<p><br>
</p>
<p>It now dies at a later stage of the compilation process.</p>
<p><br>
</p>
<p>...<br>
</p>
<p></p>
<div>[tests/caen_v792.c:73: IPEDConversion]<br>
[tests/caen_v820.c:32: DefaultConfig]<br>
2024-02-08,16:59:58:INFO: Will try default cfg path='/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/nurdlib/cfg/default', can be set with NURDLIB_DEF_PATH. [config/config.c:181]<br>
2024-02-08,16:59:58:INFO: Opened './tests/caen_v820_empty.cfg' { [config/parser.c:287]<br>
2024-02-08,16:59:58:INFO: .Opened '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/nurdlib/cfg/default/caen_v820.cfg' { [config/parser.c:287]<br>
2024-02-08,16:59:58:INFO: .Closed '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/nurdlib/cfg/default/caen_v820.cfg' } [config/parser.c:299]<br>
2024-02-08,16:59:58:INFO: .Opened '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/nurdlib/cfg/default/module_log_level.cfg' { [config/parser.c:287]<br>
2024-02-08,16:59:58:INFO: .Closed '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/nurdlib/cfg/default/module_log_level.cfg' } [config/parser.c:299]<br>
2024-02-08,16:59:58:INFO: Closed './tests/caen_v820_empty.cfg' } [config/parser.c:299]<br>
2024-02-08,16:59:58:ERRR: Could not find keyword config 'paux'. [config/config.c:711]<br>
2024-02-08,16:59:58:ERRR: Calling abort()... [config/config.c:711]<br>
make: *** [build_cc_ppc-linux_4.2.2_debug/test_ok] Error 1</div>
<br>
<p></p>
<p>The problem is that the environment variable NURDLIB_DEF_PATH is still set to the old directory (<span>'2023_mcalstruck'</span> instead of
<span>'2024_mcalstruck', which I created today)</span>. Of course, I can change this now. But is there a list of all the environment variables that need to be updated? Or is <span>NURDLIB_DEF_PATH</span> the only one?</p>
<p><br>
</p>
<p><br>
</p>
<p>Best greetings</p>
<p>Günter<br>
</p>
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
<b>Gesendet:</b> Montag, 8. Januar 2024 14:19:41<br>
<b>An:</b> Weber, Guenter Dr.; Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
<b>Betreff:</b> Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to update to the most recent version</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">I have pushed a new version to Gitlab that builds on a rio4 with the
<br>
same mapping and trlo ii support.<br>
<br>
*Crossing fingers*<br>
<br>
Cheers,<br>
<br>
Hans<br>
<br>
On 2024-01-08 11:46, Hans Toshihide Törnqvist wrote:<br>
> This is on me... Somehow I keep reintroducing this problem (: I will <br>
> look for a similar running rio4 and build this myself and give you a new <br>
> version.<br>
> <br>
> Cheers,<br>
> <br>
> Hans<br>
> <br>
> On 2024-01-08 11:44, Weber, Guenter Dr. wrote:<br>
>> Alright. Sorry for being stupid!<br>
>><br>
>><br>
>> With 'make' everything runs smoothly up to this point:<br>
>><br>
>><br>
>> ...<br>
>><br>
>> SUITE build_cc_ppc-linux_4.2.2_debug/ntest/tests/fail.suite<br>
>> SUITE build_cc_ppc-linux_4.2.2_debug/ntest/tests/fixture.suite<br>
>> SUITE build_cc_ppc-linux_4.2.2_debug/ntest/tests/pass.suite<br>
>> SUITE build_cc_ppc-linux_4.2.2_debug/ntest/tests/signal.suite<br>
>> SUITE build_cc_ppc-linux_4.2.2_debug/ntest/tests/string.suite<br>
>> SUITE build_cc_ppc-linux_4.2.2_debug/ntest/tests/verbose.suite<br>
>> SUITS build_cc_ppc-linux_4.2.2_debug/ntest/tests/ntest_.suites<br>
>> NTEST build_cc_ppc-linux_4.2.2_debug/ntest/tests/ntest_.c<br>
>> CCGEN build_cc_ppc-linux_4.2.2_debug/ntest/tests/ntest_.o<br>
>> LD build_cc_ppc-linux_4.2.2_debug/test_ntest<br>
>> LD build_cc_ppc-linux_4.2.2_debug/test<br>
>> build_cc_ppc-linux_4.2.2_debug/tools/hwmap_error_internal.o:(.sdata+0x0): undefined reference to `trcom_hwmap_error_internal'<br>
>> collect2: ld returned 1 exit status<br>
>> make: *** [build_cc_ppc-linux_4.2.2_debug/test] Error 1<br>
>><br>
>><br>
>><br>
>> What should I do?<br>
>><br>
>><br>
>><br>
>><br>
>> Best greetings<br>
>><br>
>> Günter<br>
>><br>
>><br>
>><br>
>> ------------------------------------------------------------------------<br>
>> *Von:* Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
>> *Gesendet:* Montag, 8. Januar 2024 11:38:23<br>
>> *An:* Discuss use of Nurdlib, TRLO II, drasi and UCESB.; Weber, <br>
>> Guenter Dr.<br>
>> *Betreff:* Re: [subexp-daq] NURDLIB: - how to check which version is <br>
>> installed and how to update to the most recent version<br>
>> Dear Günter,<br>
>><br>
>> Aha, it looks like Hċkan's instructions could be misinterpreted, what<br>
>> you are seeing is expected behaviour :)<br>
>><br>
>> 'make clean' will clean the build directory, which it does with 'rm -rf<br>
>> build_...'.<br>
>><br>
>> 'make' without additional arguments builds nurdlib which is what you<br>
>> want now.<br>
>><br>
>> Cheers,<br>
>> Hans<br>
>><br>
>> On 2024-01-08 11:29, Weber, Guenter Dr. wrote:<br>
>>> Dear Hans,<br>
>>><br>
>>><br>
>>> I copied the directory of our existing DAQ system:<br>
>>><br>
>>> > cp -r old_daq new_daq<br>
>>><br>
>>><br>
>>> Then deleted the NURDLIB folder, downloaded the new one and switched <br>
>>> to the mcal_daq_merge branch using<br>
>>><br>
>>> > git checkout mcal_daq_merge<br>
>>><br>
>>><br>
>>> Then I connected to the RIO and tried to compile in the folder of the <br>
>>> new NURDLIB. This is the result:<br>
>>><br>
>>> RIO4-MCAL-2 mbsdaq > make clean<br>
>>> Could not figure out RFX1 firmware (8-xdigit number), skipping.<br>
>>> TRIDI_FW=d374466d<br>
>>> VULOM4_FW=d96ffc88<br>
>>> RFX1_FW=<br>
>>> rm -rf build_cc_ppc-linux_4.2.2_debug<br>
>>><br>
>>><br>
>>> No further message and a new folder build_cc_ppc-linux_4.2.2_debug is <br>
>>> not created.<br>
>>><br>
>>><br>
>>> When checking the Makefile, I noticed that in the old NURDLIB folder <br>
>>> there is no /gmake, instead there is a file make.mk which probably <br>
>>> does the same job.<br>
>>><br>
>>><br>
>>> Probably there are some adjustment that I need to make, so that the <br>
>>> new NURDLIB version can compile on our system. But I don't know where <br>
>>> to look at, unfortunately.<br>
>>><br>
>>><br>
>>> Could you give us advice?<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> Best greetings<br>
>>><br>
>>> Günter<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> ------------------------------------------------------------------------<br>
>>> *Von:* subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag <br>
>>> von Hċkan T Johansson <f96hajo@chalmers.se><br>
>>> *Gesendet:* Sonntag, 7. Januar 2024 21:48:21<br>
>>> *An:* Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
>>> *Betreff:* Re: [subexp-daq] NURDLIB: - how to check which version is <br>
>>> installed and how to update to the most recent version<br>
>>><br>
>>> Dear Günter,<br>
>>><br>
>>> I would very much suggest to do the 'update' in a copy of the directory<br>
>>> tree that you are using, such that it is very easy to go back. (Or go<br>
>>> between the systems.)<br>
>>><br>
>>> For the update, something along the lines:<br>
>>><br>
>>> git fetch origin # or instead of 'origin' the shorthand you have <br>
>>> for the<br>
>>> # remote repo<br>
>>><br>
>>> git log --all --decorate --graph --oneline --color # just to see where<br>
>>> # you are, and where you <br>
>>> would go<br>
>>><br>
>>> git checkout mcal_daq_merge # if that fails, try <br>
>>> origin/mcal_daq_merge<br>
>>><br>
>>><br>
>>> You would want to run the git commands etc on the PC, but <br>
>>> compilations of<br>
>>> code that runs on the RIO needs to be done on the RIO.<br>
>>><br>
>>> A 'make clean' is probbaly a healthy start.<br>
>>><br>
>>> But first - please make sure to work in copied directory tree.<br>
>>><br>
>>> Cheers,<br>
>>> Hċkan<br>
>>><br>
>>><br>
>>><br>
>>> On Sun, 7 Jan 2024, Weber, Guenter Dr. wrote:<br>
>>><br>
>>>><br>
>>>> Dear Hans,<br>
>>>><br>
>>>><br>
>>>> thank you very much and have a happy new year!<br>
>>>><br>
>>>><br>
>>>> Could you give me instructions on how to update NURDLIB in an already<br>
>>>> existing DAQ system?<br>
>>>><br>
>>>><br>
>>>> Would it be enough to replace the old files in the NURDLIB folder <br>
>>>> with the<br>
>>>> most recent ones and then somewhere type in "make"? And is <br>
>>>> compilation to be<br>
>>>> executed within the RIO system or on the server?<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> Best greetings from Jena<br>
>>>><br>
>>>> Günter<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> ____________________________________________________________________________<br>
>>>> Von: Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
>>>> Gesendet: Sonntag, 7. Januar 2024 20:33:55<br>
>>>> An: Weber, Guenter Dr.; Discuss use of Nurdlib, TRLO II, drasi and <br>
>>>> UCESB.<br>
>>>> Betreff: Re: AW: [subexp-daq] NURDLIB: - how to check which version is<br>
>>>> installed and how to update to the most recent version Dear Günter,<br>
>>>><br>
>>>> I took a shot at merging the 'mcal_daq' branch that you have been using<br>
>>>> with the 'master' branch, you can find that merge in the branch<br>
>>>> 'mcal_daq_merge'.<br>
>>>><br>
>>>> That version passes my soft tests, but they are weak compared to a real<br>
>>>> running DAQ :) So please give it a try and let me know how it goes.<br>
>>>><br>
>>>> Best regards,<br>
>>>><br>
>>>> Hans<br>
>>>><br>
>>>> On 2023-12-22 19:32, Weber, Guenter Dr. wrote:<br>
>>>> > Dear Hans,<br>
>>>> ><br>
>>>> ><br>
>>>> > the command<br>
>>>> ><br>
>>>> ><br>
>>>> > > git remote -v<br>
>>>> ><br>
>>>> ><br>
>>>> > resulted in the following output:<br>
>>>> ><br>
>>>> ><br>
>>>> > bloeher bloeher@140.181.60.97:/u/bloeher/git-bare/nurdlib-jena.git <br>
>>>> (fetch)<br>
>>>> > bloeher bloeher@140.181.60.97:/u/bloeher/git-bare/nurdlib-jena.git <br>
>>>> (push)<br>
>>>> > maxs1 > <br>
>>>> atpnbg011:/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2021_mcalstruck/nurdlib<br>
>>>> > (fetch)<br>
>>>> > maxs1 > <br>
>>>> atpnbg011:/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2021_mcalstruck/nurdlib<br>
>>>> (push)<br>
>>>> > origin /u/htoernqv/repos/nurdlib.git/ (fetch)<br>
>>>> > origin /u/htoernqv/repos/nurdlib.git/ (push)<br>
>>>> ><br>
>>>> > I added the new git repository and executed the push command as<br>
>>>> > explained in your e-mail. Looks like everything worked out fine.<br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > Best greetings<br>
>>>> ><br>
>>>> > Günter<br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > <br>
>>>> ------------------------------------------------------------------------<br>
>>>> > *Von:* Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
>>>> > *Gesendet:* Freitag, 22. Dezember 2023 18:25:05<br>
>>>> > *An:* Discuss use of Nurdlib, TRLO II, drasi and UCESB.; Weber, <br>
>>>> Guenter<br>
>>>> Dr.<br>
>>>> > *Betreff:* Re: [subexp-daq] NURDLIB: - how to check which version is<br>
>>>> > installed and how to update to the most recent version<br>
>>>> > Dear Günter,<br>
>>>> ><br>
>>>> > On 2023-12-22 17:55, Weber, Guenter Dr. wrote:<br>
>>>> >> Dear Hakan,<br>
>>>> >><br>
>>>> >> thank you very much for the reply.<br>
>>>> >><br>
>>>> >> On my system the output of the command is as follows:<br>
>>>> >><br>
>>>> >> git describe --all --always --dirty --long<br>
>>>> >> -> heads/mcal_daq-0-gb2bc721<br>
>>>> >><br>
>>>> >> How shall I interpret this output?<br>
>>>> ><br>
>>>> > It looks like your repository has the branch 'mcal_daq' active, <br>
>>>> and part<br>
>>>> > of the checksum is b2bc721.<br>
>>>> ><br>
>>>> > The very good news is that it doesn't say "-dirty" at the end, which<br>
>>>> > means that there are no uncommitted changes, yet :)<br>
>>>> ><br>
>>>> >> I guess I should compare it to something I can find under<br>
>>>> >> <a href="https://gitlab.com/chalmers-subexp">https://gitlab.com/chalmers-subexp</a>
<br>
>>>> <<a href="https://gitlab.com/chalmers-subexp">https://gitlab.com/chalmers-subexp</a>>
<br>
>> <<a href=""></a>https://gitlab.com/chalmers-subexp <<a href="https://gitlab.com/chalmers-subexp">https://gitlab.com/chalmers-subexp</a>>><br>
>>> <<a href=""></a>https://gitlab.com/chalmers-subexp <<a href=""></a>https://gitlab.com/chalmers-subexp
<br>
>> <<a href="https://gitlab.com/chalmers-subexp">https://gitlab.com/chalmers-subexp</a>>>><br>
>>>> > <<a href=""></a>https://gitlab.com/chalmers-subexp <br>
>>>> <<a href=""></a>https://gitlab.com/chalmers-subexp<br>
>>> <<a href=""></a>https://gitlab.com/chalmers-subexp <br>
>>> <<a href="https://gitlab.com/chalmers-subexp">https://gitlab.com/chalmers-subexp</a>>>>><br>
>>>> ><br>
>>>> > It seems like the branch/commit are not in any of the "official"<br>
>>>> > repositories, I had a look. However, I did find 'mcal_daq' <br>
>>>> branches in<br>
>>>> > some private repositories at GSI by Bastii, but I cannot find the<br>
>>>> > b2bc721 commit. I also cannot find several of the commit messages.<br>
>>>> ><br>
>>>> > The safest way forward would be if you could push your version of<br>
>>>> > nurdlib to gitlab. It looks like you are currently a member of the<br>
>>>> > project, so try:<br>
>>>> ><br>
>>>> > > git remote -v<br>
>>>> ><br>
>>>> > If the gitlab repo is not listed there, do:<br>
>>>> ><br>
>>>> > > git remote add gitlab git@gitlab.com:chalmers-subexp/nurdlib.git<br>
>>>> ><br>
>>>> > Then:<br>
>>>> ><br>
>>>> > > git push gitlab mcal_daq<br>
>>>> ><br>
>>>> > I can then pull that and see how to get that into the main branch. <br>
>>>> Once<br>
>>>> > that's done, I will ask you to try the new version to make sure it <br>
>>>> still<br>
>>>> > runs correctly. And of course if there are problems with the above<br>
>>>> > commands, let us know.<br>
>>>> ><br>
>>>> > Best regards,<br>
>>>> ><br>
>>>> > Hans<br>
>>>> ><br>
>>>> >> But there I only can access the following projects:<br>
>>>> >><br>
>>>> >> - drasi<br>
>>>> >> - egmwsort<br>
>>>> >> - ucesb<br>
>>>> >><br>
>>>> >> Best greetings<br>
>>>> >> Günter<br>
>>>> >><br>
>>>> >><br>
>>>> >> <br>
>>>> ------------------------------------------------------------------------<br>
>>>> >> *Von:* subexp-daq <subexp-daq-bounces@lists.chalmers.se> im <br>
>>>> Auftrag von<br>
>>>> >> Hċkan T Johansson <f96hajo@chalmers.se><br>
>>>> >> *Gesendet:* Freitag, 22. Dezember 2023 17:48:46<br>
>>>> >> *An:* Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
>>>> >> *Betreff:* Re: [subexp-daq] NURDLIB: - how to check which version is<br>
>>>> >> installed and how to update to the most recent version<br>
>>>> >><br>
>>>> >> Dear Günter,<br>
>>>> >><br>
>>>> >> On Fri, 22 Dec 2023, Weber, Guenter Dr. wrote:<br>
>>>> >><br>
>>>> >>><br>
>>>> >>> Dear all,<br>
>>>> >>><br>
>>>> >>><br>
>>>> >>> I would like to know how ...<br>
>>>> >>><br>
>>>> >>><br>
>>>> >>> 1) I can check which version of NURDLIB is installed on my system.<br>
>>>> >><br>
>>>> >> Please somewhere under the nurdlib/ directory, run:<br>
>>>> >><br>
>>>> >> git describe --all --always --dirty --long<br>
>>>> >><br>
>>>> >>> 2) I can update to the most recent 'official' version.<br>
>>>> >><br>
>>>> >> cd <directory-where-the-new-copy-should-be-under><br>
>>>> >><br>
>>>> >> git clone git@gitlab.com:chalmers-subexp/nurdlib.git<br>
>>>> >><br>
>>>> >> Then:<br>
>>>> >><br>
>>>> >> cd nurdlib<br>
>>>> >><br>
>>>> >> For that git clone to work, you'll first have to set up ssh keys <br>
>>>> with<br>
>>>> >> gitlab. That would be useful also in order to upload code. See:<br>
>>>> >><br>
>>>> >> <a href="https://docs.gitlab.com/ee/user/ssh.html">https://docs.gitlab.com/ee/user/ssh.html</a>
<br>
>> <<a href="https://docs.gitlab.com/ee/user/ssh.html">https://docs.gitlab.com/ee/user/ssh.html</a>><br>
>>> <<a href=""></a>https://docs.gitlab.com/ee/user/ssh.html <br>
>> <<a href="https://docs.gitlab.com/ee/user/ssh.html">https://docs.gitlab.com/ee/user/ssh.html</a>>><br>
>>>> > <<a href=""></a>https://docs.gitlab.com/ee/user/ssh.html<br>
>>> <<a href=""></a>https://docs.gitlab.com/ee/user/ssh.html <br>
>> <<a href="https://docs.gitlab.com/ee/user/ssh.html">https://docs.gitlab.com/ee/user/ssh.html</a>>>><br>
>>>> >> <<a href=""></a>https://docs.gitlab.com/ee/user/ssh.html<br>
>>>> > <<a href=""></a>https://docs.gitlab.com/ee/user/ssh.html<br>
>>> <<a href=""></a>https://docs.gitlab.com/ee/user/ssh.html <br>
>> <<a href="https://docs.gitlab.com/ee/user/ssh.html">https://docs.gitlab.com/ee/user/ssh.html</a>>>>><br>
>>>> >><br>
>>>> >> and please *do* use a passphrase for the ssh key.<br>
>>>> >><br>
>>>> >> Cheers,<br>
>>>> >> Hċkan<br>
>>>> >><br>
>>>> >><br>
>>>> >>><br>
>>>> >>><br>
>>>> >>> Thank you very much!<br>
>>>> >>><br>
>>>> >>><br>
>>>> >>><br>
>>>> >>> Best greetings<br>
>>>> >>><br>
>>>> >>> Günter<br>
>>>> >>><br>
>>>> >>><br>
>>>> >>><br>
>>>> >>><br>
>>>> >><br>
>>>><br>
>>>><br>
>>><br>
-- <br>
subexp-daq mailing list<br>
subexp-daq@lists.chalmers.se<br>
<a href="https://lists.chalmers.se/mailman/listinfo/subexp-daq">https://lists.chalmers.se/mailman/listinfo/subexp-daq</a><br>
</div>
</span></font>
</body>
</html>