<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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><div dir="auto">Dear Günter,<br><br>Those command lines executed for the compilation are really long, and have several mentions of trloii with various versions (ie both empty and with a number). Silly question, but did you run a make clean before rebuilding both nurdlib and r3bfuser?<br><br>Have a good weekend,<br><br>Hans<br></div><br><br><div class="gmail_quote"><div dir="auto">"Weber, Guenter Dr." <g.weber@hi-jena.gsi.de> skrev: (12 januari 2024 20:21:54 CET)</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<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>I unset the paths as you suggested. Then I compiled NURDLIB again (this time it showed me different firmware numbers at the start). </p>
<p><br>
</p>
<p>And then something went wrong with R3DFSUSER compilation:</p>
<p><br>
</p>
<p></p>
<div><span style="font-size:8pt">RIO4-MCAL-1 mbsdaq > make drasi</span></div>
<div><span style="font-size:8pt">rm -f build_cc_ppc-linux_4.2.2_debug</span></div>
<div><span style="font-size:8pt">[ -d build_cc_ppc-linux_4.2.2_debug_drasi ] || mkdir -p build_cc_ppc-linux_4.2.2_debug_drasi</span></div>
<div><span style="font-size:8pt">ln -s build_cc_ppc-linux_4.2.2_debug_drasi build_cc_ppc-linux_4.2.2_debug</span></div>
<div><span style="font-size:8pt">make -f Makefile.drasi</span></div>
<div><span style="font-size:8pt">make[1]: Entering directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'</span></div>
<div><span style="font-size:8pt">NCONF build_cc_ppc-linux_4.2.2_debug/nconf.args</span></div>
<div><span style="font-size:8pt">udp.h: Could not configure module UDP, build_cc_ppc-linux_4.2.2_debug/nconf/udp.h.log:</span></div>
<div><span style="font-size:8pt">=== UDP:ARPA_INET_H ===</span></div>
<div><span style="font-size:8pt">run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.c -I. -I build_cc_ppc-linux_4.2.2_debug/nconfing/ -c -DNCONFING_mUDP=1 -DDRASI -I. -Ibuild_cc_ppc-linux_4.2.2_debug
-DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/gen_gen_ppc-linux_4.2.2 -I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809
-pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi -I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/dtc_arch
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/hwmap -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo/gen_ppc-linux_4.2.2 -ggdb
-Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow -maltivec -mregnames</span></div>
<div><span style="font-size:8pt">run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.bin build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o -I. -I build_cc_ppc-linux_4.2.2_debug/nconfing/ -DDRASI -I. -Ibuild_cc_ppc-linux_4.2.2_debug -DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/gen_gen_ppc-linux_4.2.2
-I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2 -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809 -pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi
-I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/dtc_arch -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/hwmap
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo/gen_ppc-linux_4.2.2 -ggdb -Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow
-maltivec -mregnames -L../nurdlib/build_cc_ppc-linux_4.2.2_debug -L/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/hwmap/lib_ppc-linux_4.2.2 /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a
/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/common/lib_ppc-linux_4.2.2/trcomlib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a
-lhwmap /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/common/lib_ppc-linux_4.2.2/trcomlib.a /mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/lib/libetherbone.a -lcesXpcLib -lcesDma -lm -lrt -pthread -lnurdlib -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/lib_ppc-linux_4.2.2
-llwroc_mbscompat -llwroc_main -llwroc_readout -llwroc_nofilter -llwroc -llwroc_netutil -llwroc_parseutil -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../hwmap/lib_ppc-linux_4.2.2 -lhwmap -lpthread -lrt -lm -lcesXpcLib -lncurses -llwroc_hwmap_error</span></div>
<div><span style="font-size:8pt">cc: /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a: No such file or directory</span></div>
<div><span style="font-size:8pt">cc: /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a: No such file or directory</span></div>
<div><span style="font-size:8pt">Failed.</span></div>
<div><span style="font-size:8pt">=== UDP:NETINET_IN_H ===</span></div>
<div><span style="font-size:8pt">run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.c -I. -I build_cc_ppc-linux_4.2.2_debug/nconfing/ -c -DNCONFING_mUDP=1 -DDRASI -I. -Ibuild_cc_ppc-linux_4.2.2_debug
-DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/gen_gen_ppc-linux_4.2.2 -I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809
-pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi -I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/dtc_arch
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/hwmap -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo/gen_ppc-linux_4.2.2 -ggdb
-Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow -maltivec -mregnames</span></div>
<div><span style="font-size:8pt">run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.bin build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o -I. -I build_cc_ppc-linux_4.2.2_debug/nconfing/ -DDRASI -I. -Ibuild_cc_ppc-linux_4.2.2_debug -DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/gen_gen_ppc-linux_4.2.2
-I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2 -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809 -pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi
-I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/dtc_arch -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/hwmap
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo/gen_ppc-linux_4.2.2 -ggdb -Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow
-maltivec -mregnames -L../nurdlib/build_cc_ppc-linux_4.2.2_debug -L/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/hwmap/lib_ppc-linux_4.2.2 /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a
/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/common/lib_ppc-linux_4.2.2/trcomlib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a
-lhwmap /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/common/lib_ppc-linux_4.2.2/trcomlib.a /mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/lib/libetherbone.a -lcesXpcLib -lcesDma -lm -lrt -pthread -lnurdlib -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/lib_ppc-linux_4.2.2
-llwroc_mbscompat -llwroc_main -llwroc_readout -llwroc_nofilter -llwroc -llwroc_netutil -llwroc_parseutil -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../hwmap/lib_ppc-linux_4.2.2 -lhwmap -lpthread -lrt -lm -lcesXpcLib -lncurses -llwroc_hwmap_error</span></div>
<div><span style="font-size:8pt">cc: /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a: No such file or directory</span></div>
<div><span style="font-size:8pt">cc: /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a: No such file or directory</span></div>
<div><span style="font-size:8pt">Failed.</span></div>
<div><span style="font-size:8pt">=== UDP:BSD_IN_H ===</span></div>
<div><span style="font-size:8pt">run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.c -I. -I build_cc_ppc-linux_4.2.2_debug/nconfing/ -c -DNCONFING_mUDP=1 -DDRASI -I. -Ibuild_cc_ppc-linux_4.2.2_debug
-DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/gen_gen_ppc-linux_4.2.2 -I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809
-pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi -I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/dtc_arch
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/hwmap -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo/gen_ppc-linux_4.2.2 -ggdb
-Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow -maltivec -mregnames</span></div>
<div><span style="font-size:8pt">run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.bin build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o -I. -I build_cc_ppc-linux_4.2.2_debug/nconfing/ -DDRASI -I. -Ibuild_cc_ppc-linux_4.2.2_debug -DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/gen_gen_ppc-linux_4.2.2
-I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2 -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809 -pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi
-I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/dtc_arch -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/hwmap
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo/gen_ppc-linux_4.2.2 -ggdb -Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow
-maltivec -mregnames -L../nurdlib/build_cc_ppc-linux_4.2.2_debug -L/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/hwmap/lib_ppc-linux_4.2.2 /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a
/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/common/lib_ppc-linux_4.2.2/trcomlib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_1409285e_trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a
-lhwmap /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/common/lib_ppc-linux_4.2.2/trcomlib.a /mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/lib/libetherbone.a -lcesXpcLib -lcesDma -lm -lrt -pthread -lnurdlib -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/lib_ppc-linux_4.2.2
-llwroc_mbscompat -llwroc_main -llwroc_readout -llwroc_nofilter -llwroc -llwroc_netutil -llwroc_parseutil -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../hwmap/lib_ppc-linux_4.2.2 -lhwmap -lpthread -lrt -lm -lcesXpcLib -lncurses -llwroc_hwmap_error</span></div>
<div><span style="font-size:8pt">cc: /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a: No such file or directory</span></div>
<div><span style="font-size:8pt">cc: /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw__trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a: No such file or directory</span></div>
<div><span style="font-size:8pt">Failed.</span></div>
<div><span style="font-size:8pt">make[1]: *** [build_cc_ppc-linux_4.2.2_debug/nconf.args] Error 1</span></div>
<div><span style="font-size:8pt">make[1]: Leaving directory `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'</span></div>
<div><span style="font-size:8pt">make: *** [drasi] Error 2</span></div>
<br>
<p></p>
<p><br>
</p>
<p>To me it looks like the firmware variable is empty now, right?</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Best greetings and have a nice weekend</p>
<p>Günter</p>
<p><br>
</p>
<p><br>
</p>
<div id="x_Signature">
<div style="font-family:Tahoma; font-size:13px"></div>
</div>
</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> Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
<b>Gesendet:</b> Freitag, 12. Januar 2024 16:16:54<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.; Weber, Guenter Dr.<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">Dear Günter,<br>
<br>
---<br>
<br>
Let's start with the nurdlib build:<br>
<br>
The *_FW env vars are selected by nurdlib/Makefile by looking at the <br>
available $TRLOII_PATH/trloctrl/fw_* directories. Except, if they were <br>
already set!<br>
This lets the user control exactly (some of) the decisions made by <br>
nurdlib, otherwise the machines will take over.<br>
<br>
Probably there are some lines in ~/.tcshrc or a similar file which sets <br>
them. Try commenting them out, log out of the Rio4, log back in, "make <br>
clean" and already then you should see which firmwares are selected. <br>
Then run "make". You could also set *_FW explicitly to the new firmware <br>
if you prefer or the auto-selection doesn't work.<br>
<br>
I am working on the nurdlib documentation, actually even on the <br>
enviroment variable section right now, so I'll add this in :)<br>
<br>
So, for nurdlib, please check the env vars:<br>
- TRLOII_PATH<br>
- TRIDI_FW<br>
- VULOM4_FW<br>
<br>
---<br>
<br>
r3bfuser build:<br>
<br>
I am guessing that this is related to mismatching firmware numbers, the <br>
build pulls data from what nurdlib decided. If nurdlib builds with the <br>
correct numbers as described above, I hope r3bfuser will "just work" <br>
(crossing all my fingers).<br>
<br>
---<br>
<br>
The *_CTRL variables are not used by nurdlib and r3bfuser, and are only <br>
convenient on the cmd-line by for example:<br>
<br>
$TRIDI_CTRL --addr=n --print-config<br>
<br>
But they should point to the correct trloctrl builds for your new <br>
firmware or they will complain when they talk to the hardware!<br>
<br>
---<br>
<br>
Cheers,<br>
<br>
Hans<br>
<br>
On 2024-01-12 15:33, Weber, Guenter Dr. wrote:<br>
> Dear friends,<br>
> <br>
> <br>
> I did set up a second DAQ system and followed the instructions provided by<br>
> <br>
> <br>
> Everything goes smoothly (I had to use the workaround in TRLOII) until <br>
> compilation of R3DFUSER. This is the output (compilation done on the RIO):<br>
> <br>
> <br>
> RIO4-MCAL-1 mbsdaq > make drasi<br>
> rm -f build_cc_ppc-linux_4.2.2_debug<br>
> [ -d build_cc_ppc-linux_4.2.2_debug_drasi ] || mkdir -p <br>
> build_cc_ppc-linux_4.2.2_debug_drasi<br>
> ln -s build_cc_ppc-linux_4.2.2_debug_drasi build_cc_ppc-linux_4.2.2_debug<br>
> make -f Makefile.drasi<br>
> make[1]: Entering directory <br>
> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
> NCONF build_cc_ppc-linux_4.2.2_debug/nconf.args<br>
> udp.h: Could not configure module UDP, <br>
> build_cc_ppc-linux_4.2.2_debug/nconf/udp.h.log:<br>
> === UDP:ARPA_INET_H ===<br>
> run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.c -I. -I <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/ -c -DNCONFING_mUDP=1 -DDRASI <br>
> -I. -Ibuild_cc_ppc-linux_4.2.2_debug <br>
> -DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii <br>
> -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/gen_gen_ppc-linux_4.2.2 -I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809
-pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi -I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -ggdb -Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow -maltivec -mregnames<br>
> run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.bin <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o -I. -I <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/ -DDRASI -I. <br>
> -Ibuild_cc_ppc-linux_4.2.2_debug <br>
> -DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii <br>
> -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/gen_gen_ppc-linux_4.2.2 -I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809
-pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi -I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -ggdb -Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow -maltivec -mregnames -L../nurdlib/build_cc_ppc-linux_4.2.2_debug
/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/common/lib_ppc-linux_4.2.2/trcomlib.a
/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/lib/libetherbone.a -lcesXpcLib -lcesDma -lm -lrt -pthread -lnurdlib -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/lib_ppc-linux_4.2.2 -llwroc_mbscompat -llwroc_main -llwroc_readout
-llwroc_nofilter -llwroc -llwroc_netutil -llwroc_parseutil -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../hwmap/lib_ppc-linux_4.2.2 -lhwmap -lpthread -lrt -lm -lcesXpcLib -lncurses -llwroc_hwmap_error<br>
> cc: <br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a: No such file or directory<br>
> cc: <br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a: No such file or directory<br>
> Failed.<br>
> === UDP:NETINET_IN_H ===<br>
> run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.c -I. -I <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/ -c -DNCONFING_mUDP=1 -DDRASI <br>
> -I. -Ibuild_cc_ppc-linux_4.2.2_debug <br>
> -DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii <br>
> -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/gen_gen_ppc-linux_4.2.2 -I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809
-pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi -I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -ggdb -Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow -maltivec -mregnames<br>
> run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.bin <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o -I. -I <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/ -DDRASI -I. <br>
> -Ibuild_cc_ppc-linux_4.2.2_debug <br>
> -DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii <br>
> -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/gen_gen_ppc-linux_4.2.2 -I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809
-pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi -I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -ggdb -Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow -maltivec -mregnames -L../nurdlib/build_cc_ppc-linux_4.2.2_debug
/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/common/lib_ppc-linux_4.2.2/trcomlib.a
/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/lib/libetherbone.a -lcesXpcLib -lcesDma -lm -lrt -pthread -lnurdlib -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/lib_ppc-linux_4.2.2 -llwroc_mbscompat -llwroc_main -llwroc_readout
-llwroc_nofilter -llwroc -llwroc_netutil -llwroc_parseutil -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../hwmap/lib_ppc-linux_4.2.2 -lhwmap -lpthread -lrt -lm -lcesXpcLib -lncurses -llwroc_hwmap_error<br>
> cc: <br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a: No such file or directory<br>
> cc: <br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a: No such file or directory<br>
> Failed.<br>
> === UDP:BSD_IN_H ===<br>
> run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.c -I. -I <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/ -c -DNCONFING_mUDP=1 -DDRASI <br>
> -I. -Ibuild_cc_ppc-linux_4.2.2_debug <br>
> -DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii <br>
> -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/gen_gen_ppc-linux_4.2.2 -I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809
-pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi -I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -ggdb -Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow -maltivec -mregnames<br>
> run: cc -o build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.bin <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/nconf/udp.h.o -I. -I <br>
> build_cc_ppc-linux_4.2.2_debug/nconfing/ -DDRASI -I. <br>
> -Ibuild_cc_ppc-linux_4.2.2_debug <br>
> -DTRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii <br>
> -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/gen_ppc-linux_4.2.2 -I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo
-I/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/gen_gen_ppc-linux_4.2.2 -I../nurdlib -I../nurdlib/include -I../nurdlib/build_cc_ppc-linux_4.2.2_debug -I../nurdlib/build_cc_ppc-linux_4.2.2_debug/replacements -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/gen_ppc-linux_4.2.2
-I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat -I /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../f_user_daq -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809
-pthread -I/usr/include/ces/cesXpcLib -I/usr/include/ces/cesOsApi -I/usr/include/ces/cesDma -I/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/include -ggdb -Wextra -fstrict-aliasing -Wstrict-aliasing -Wstrict-overflow -maltivec -mregnames -L../nurdlib/build_cc_ppc-linux_4.2.2_debug
/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/common/lib_ppc-linux_4.2.2/trcomlib.a
/mbs/driv/white_rabbit/cherry/RIO4_Linux_OSV_2_6_33_SuHa/lib/libetherbone.a -lcesXpcLib -lcesDma -lm -lrt -pthread -lnurdlib -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/lib_ppc-linux_4.2.2 -llwroc_mbscompat -llwroc_main -llwroc_readout
-llwroc_nofilter -llwroc -llwroc_netutil -llwroc_parseutil -L/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../hwmap/lib_ppc-linux_4.2.2 -lhwmap -lpthread -lrt -lm -lcesXpcLib -lncurses -llwroc_hwmap_error<br>
> cc: <br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/lib_ppc-linux_4.2.2/tridi_ctrllib.a: No such file or directory<br>
> cc: <br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/lib_ppc-linux_4.2.2/trlo_ctrllib.a: No such file or directory<br>
> Failed.<br>
> make[1]: *** [build_cc_ppc-linux_4.2.2_debug/nconf.args] Error 1<br>
> make[1]: Leaving directory <br>
> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
> make: *** [drasi] Error 2<br>
> <br>
> I had a look at the environment variables which I took over from the <br>
> already existing system and I guess, I would need to modify some of <br>
> these lines:<br>
> <br>
> <br>
> VULOM4_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/bin_ppc-linux_4.2.2/trlo_ctrl<br>
> <br>
> TRIDI_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/bin_ppc-linux_4.2.2/tridi_ctrl<br>
> <br>
> <br>
> This is the content of the folder on the new system:<br>
> <br>
> <br>
> mbsdaq@atpnbg011:~/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl$ ls -l<br>
> insgesamt 52<br>
> drwxr-sr-x 2 mbsdaq users 4096 Jan 12 13:57 examples<br>
> -rwxr-xr-x 1 mbsdaq users 7389 Jan 12 13:57 find_firmwares.pl<br>
> -rw-r--r-- 1 mbsdaq users 114 Jan 12 15:02 firmwaredirs<br>
> drwxr-sr-x 2 mbsdaq users 4096 Jan 12 15:00 fw_0866c243_rfx1<br>
> lrwxrwxrwx 1 mbsdaq users 16 Jan 12 15:00 fw_1409285e_trlo -> <br>
> fw_6e4ba1a9_trlo<br>
> drwxr-sr-x 2 mbsdaq users 4096 Jan 12 15:00 fw_5e8f5ef4_tridi<br>
> drwxr-sr-x 2 mbsdaq users 4096 Jan 12 15:00 fw_68f8955e_trlo_all_in<br>
> drwxr-sr-x 14 mbsdaq users 4096 Jan 12 15:02 fw_6e4ba1a9_trlo<br>
> drwxr-sr-x 2 mbsdaq users 4096 Jan 12 15:00 fw_a1729cda_rfx0<br>
> lrwxrwxrwx 1 mbsdaq users 16 Jan 12 15:00 fw_a73c5093_trlo -> <br>
> fw_6e4ba1a9_trlo<br>
> drwxr-sr-x 2 mbsdaq users 4096 Jan 12 15:00 fw_af33ed35_trlo_big<br>
> -rw-r--r-- 1 mbsdaq users 994 Jan 12 13:57 Makefile<br>
> -rwxr-xr-x 1 mbsdaq users 662 Jan 12 13:57 trloctrl.sh<br>
> drwxr-sr-x 5 mbsdaq users 4096 Jan 12 13:57 trlolib<br>
> <br>
> I also had a look at the output at the beginning of the NURDLIB <br>
> compilation and if I understand correctly, it looks like the VULOM in <br>
> the new system has the same firmware as the one in the old system:<br>
> <br>
> <br>
> TRIDI_FW=d374466d<br>
> VULOM4_FW=d96ffc88<br>
> <br>
> What to do now?<br>
> <br>
> <br>
> <br>
> <br>
> Thank you very much!<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:* Freitag, 12. Januar 2024 14:34:24<br>
> *An:* Weber, Guenter Dr.; Håkan T Johansson<br>
> *Betreff:* Re: AW: AW: AW: AW: [subexp-daq] NURDLIB: - how to check <br>
> which version is installed and how to update to the most recent version<br>
> It looks to be mirrored from git.chalmers.se, so should work.<br>
> <br>
> Cheers,<br>
> Hans<br>
> <br>
> On 2024-01-12 14:22, Weber, Guenter Dr. wrote:<br>
>> Is the UCESB version on GITLAB also a mirror? Then I could download <br>
>> everything from GITLAB?<br>
>> <br>
>> <br>
>> ------------------------------------------------------------------------<br>
>> *Von:* Håkan T Johansson <f96hajo@chalmers.se><br>
>> *Gesendet:* Freitag, 12. Januar 2024 14:19:23<br>
>> *An:* Weber, Guenter Dr.<br>
>> *Cc:* Hans Toshihide Törnqvist<br>
>> *Betreff:* Re: AW: AW: AW: [subexp-daq] NURDLIB: - how to check which <br>
>> version is installed and how to update to the most recent version<br>
>> <br>
>> Ahh, sorry about that, please try with<br>
>> <br>
>> <a href="https://git.chalmers.se/expsubphys/drasi.git">https://git.chalmers.se/expsubphys/drasi.git</a>
<br>
> <<a href="https://git.chalmers.se/expsubphys/drasi.git">https://git.chalmers.se/expsubphys/drasi.git</a>><br>
>> <<a href=""></a>https://git.chalmers.se/expsubphys/drasi.git <br>
> <<a href="https://git.chalmers.se/expsubphys/drasi.git">https://git.chalmers.se/expsubphys/drasi.git</a>>><br>
>> <a href="https://git.chalmers.se/expsubphys/ucesb.git">https://git.chalmers.se/expsubphys/ucesb.git</a>
<br>
> <<a href="https://git.chalmers.se/expsubphys/ucesb.git">https://git.chalmers.se/expsubphys/ucesb.git</a>><br>
>> <<a href=""></a>https://git.chalmers.se/expsubphys/ucesb.git <br>
> <<a href="https://git.chalmers.se/expsubphys/ucesb.git">https://git.chalmers.se/expsubphys/ucesb.git</a>>><br>
>> <br>
>> and the drasi varsion on gitlab.com is a mirror so should work equally<br>
>> well.<br>
>> <br>
>> Cheers,<br>
>> Håkan<br>
>> <br>
>> <br>
>> <br>
>> On Fri, 12 Jan 2024, Weber, Guenter Dr. wrote:<br>
>> <br>
>>> <br>
>>> Dear Håkan,<br>
>>> <br>
>>> <br>
>>> I encountered the following issue(s):<br>
>>> <br>
>>> <br>
>>> git clone git@git.chalmers.se:expsubphys/drasi.git<br>
>>> git clone git@git.chalmers.se:expsubphys/ucesb.git<br>
>>> <br>
>>> 1) I don't have access to git.chalmers.se, only to gitlab.com.<br>
>>> 2) There is a DRASI also on gitlab.com, that I was using so far. But is it<br>
>>> the same as on git.chalmers.se?<br>
>>> <br>
>>> <br>
>>> Best greetings<br>
>>> Günter<br>
>>> <br>
>>> <br>
>>> <br>
>>> ____________________________________________________________________________<br>
>>> Von: Håkan T Johansson <f96hajo@chalmers.se><br>
>>> Gesendet: Donnerstag, 11. Januar 2024 08:15<br>
>>> An: Weber, Guenter Dr.<br>
>>> Cc: Hans Toshihide Törnqvist<br>
>>> Betreff: Re: AW: AW: [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>
>>> thanks!<br>
>>> <br>
>>> 1) may be the reason for that strange error in typedefs.h, since it may be<br>
>>> that it picks up the mystdint.h from the trloii compile but uses it in the<br>
>>> drasi header somehow - or vice versa.... (They are the same and typically<br>
>>> kept in sync, but we may here have hit a snag with the different versions<br>
>>> and an update I did a while ago...)<br>
>>> <br>
>>> 2) Should be fine, is just an attempt at indenting the pre-processor<br>
>>> directives, without having my editor unindent the code.<br>
>>> <br>
>>> <br>
>>> It sounds like a very nice plan if you have the hardware to set up a<br>
>>> second system from scratch. I have attached a short instruction on how to<br>
>>> downloading and compiling the codes from scratch.<br>
>>> <br>
>>> It would not surprise me if there already exist something like that, but<br>
>>> then we have two of them :-) If not, we can put this (with whatever fixes<br>
>>> are needed) up somewhere (gitlab wiki or so).<br>
>>> <br>
>>> I did test it - but that does not guarantee much...<br>
>>> <br>
>>> Cheers,<br>
>>> Håkan<br>
>>> <br>
>>> <br>
>>> <br>
>>> On Wed, 10 Jan 2024, Weber, Guenter Dr. wrote:<br>
>>> <br>
>>> ><br>
>>> > P.S. I looked a bit into the code that is compiled right before the error<br>
>>> > appear.<br>
>>> ><br>
>>> ><br>
>>> > I have no idea if this might causing problems, but in<br>
>>> ><br>
>>> > ../dtc_arch/acc_def/mystdint.h<br>
>>> > I found two things:<br>
>>> ><br>
>>> ><br>
>>> > 1) <br>
>>> ><br>
>>> > New version:<br>
>>> ><br>
>>> > #if ACC_DEF__MYSTDINT_stdint_h<br>
>>> > # include <stdint.h><br>
>>> > #endif<br>
>>> > /* This is a local fall-back solution, so should be last. */<br>
>>> > #if ACC_DEF__MYSTDINT_mystdint<br>
>>> ><br>
>>> > Old version:<br>
>>> ><br>
>>> > #if ACC_DEF_MYSTDINT_stdint_h<br>
>>> > # include <stdint.h><br>
>>> > #endif<br>
>>> > /* This is a local fall-back solution, so should be last. */<br>
>>> > #if ACC_DEF_MYSTDINT_mystdint<br>
>>> ><br>
>>> > (Note the double "_" before MYSTDINT.)<br>
>>> ><br>
>>> ><br>
>>> > 2)<br>
>>> ><br>
>>> > In both versions there are strange blanks after "#" at two positions:<br>
>>> ><br>
>>> > # include "acc_auto_def/mystdint.h"<br>
>>> > # define UINT64_C(v) v##ULL<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > Best greetings<br>
>>> ><br>
>>> > Günter<br>
>>> ><br>
>>> ><br>
>>> >___________________________________________________________________________<br>
>>> _<br>
>>> > Von: Weber, Guenter Dr.<br>
>>> > Gesendet: Mittwoch, 10. Januar 2024 19:32:59<br>
>>> > An: Hans Toshihide Törnqvist<br>
>>> > Betreff: AW: AW: [subexp-daq] NURDLIB: - how to check which version is<br>
>>> > installed and how to update to the most recent version <br>
>>> ><br>
>>> > Dear Hans,<br>
>>> ><br>
>>> ><br>
>>> > I could not reproduce the error from two hours ago. Nurdlib was laready<br>
>>> set<br>
>>> > to the right branch and in a second try compiled without problems on the<br>
>>> > RIO.<br>
>>> ><br>
>>> ><br>
>>> > However, we are now back at square one:<br>
>>> ><br>
>>> ><br>
>>> > RIO4-MCAL-2 mbsdaq > make drasi<br>
>>> > rm -f build_cc_ppc-linux_4.2.2_debug<br>
>>> > [ -d build_cc_ppc-linux_4.2.2_debug_drasi ] || mkdir -p<br>
>>> > build_cc_ppc-linux_4.2.2_debug_drasi<br>
>>> > ln -s build_cc_ppc-linux_4.2.2_debug_drasi build_cc_ppc-linux_4.2.2_debug<br>
>>> > make -f Makefile.drasi<br>
>>> > make[1]: Entering directory<br>
>>> > `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
>>> > NCONF build_cc_ppc-linux_4.2.2_debug/nconf.args<br>
>>> > UDP:ARPA_INET_H<br>
>>> > CC build_cc_ppc-linux_4.2.2_debug/f_user.o<br>
>>> > CC build_cc_ppc-linux_4.2.2_debug/subevent.o<br>
>>> > In file includedfrom/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscom<br>
>>> pat/<br>
>>> > s_veshe.h:6,<br>
>>> > from ./subevent.h:11,<br>
>>> > from subevent.c:1:<br>
>>> >/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/<br>
>>> <br>
>>> > typedefs.h:6: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTS8'<br>
>>> >/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/<br>
>>> <br>
>>> > typedefs.h:7: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTU8'<br>
>>> >/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/<br>
>>> <br>
>>> > typedefs.h:8: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTS4'<br>
>>> >/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/<br>
>>> <br>
>>> > typedefs.h:9: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTU4'<br>
>>> >/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/<br>
>>> <br>
>>> > typedefs.h:10: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTS2'<br>
>>> >/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/<br>
>>> <br>
>>> > typedefs.h:11: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTU2'<br>
>>> >/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/<br>
>>> <br>
>>> > typedefs.h:12: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTS1'<br>
>>> >/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/<br>
>>> <br>
>>> > typedefs.h:13: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTU1'<br>
>>> > In file included from ./subevent.h:11,<br>
>>> > from subevent.c:1:<br>
>>> >/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompat/<br>
>>> <br>
>>> > s_veshe.h:11: error: expected specifier-qualifier-list before 'INTS4'<br>
>>> > subevent.c: In function 'begin_goosy_vme_subevent':<br>
>>> > subevent.c:12: error: 's_veshe' has no member named 'l_dlen'<br>
>>> > subevent.c: In function 'end_goosy_vme_subevent':<br>
>>> > subevent.c:45: error: 's_veshe' has no member named 'l_dlen'<br>
>>> > make[1]: *** [build_cc_ppc-linux_4.2.2_debug/subevent.o] Error 1<br>
>>> > make[1]: Leaving directory<br>
>>> > `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
>>> > make: *** [drasi] Error 2<br>
>>> > RIO4-MCAL-2 mbsdaq ><br>
>>> ><br>
>>> > Thus, downloading and recompiling DRASI, NURDLIB, and R3BFUSER did not<br>
>>> solve<br>
>>> > the problem with the latter.<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > ��<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > Best greetings<br>
>>> ><br>
>>> > Günter<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> >___________________________________________________________________________<br>
>>> _<br>
>>> > Von: Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
>>> > Gesendet: Mittwoch, 10. Januar 2024 18:24:21<br>
>>> > An: Weber, Guenter Dr.<br>
>>> > Betreff: Re: AW: [subexp-daq] NURDLIB: - how to check which version is<br>
>>> > installed and how to update to the most recent version <br>
>>> > Sorry I got held up.<br>
>>> ><br>
>>> > I compiled 'mcal_daq_merge' from Gitlab on a rio4 just fine, so I am<br>
>>> > just as puzzled where those event buffer test errors come from...<br>
>>> ><br>
>>> > Any luck with a 'make clean && make'?<br>
>>> ><br>
>>> > Cheers,<br>
>>> ><br>
>>> > Hans<br>
>>> ><br>
>>> > On 2024-01-10 17:36, Weber, Guenter Dr. wrote:<br>
>>> > > Dear Hans,<br>
>>> > ><br>
>>> > ><br>
>>> > > now things really get weird.<br>
>>> > ><br>
>>> > ><br>
>>> > > I again downloaded NURDLIB, DRASI, and R3BFUSER. DRASI compiled without<br>
>>> > > problems (first on PC, then on RIO).<br>
>>> > ><br>
>>> > ><br>
>>> > > Now NURDLIB compilation stops with an error:<br>
>>> > ><br>
>>> > ><br>
>>> > > LD build_cc_ppc-linux_4.2.2_debug/test_ntest<br>
>>> > > LD build_cc_ppc-linux_4.2.2_debug/test<br>
>>> > > /bin/sh: line 1: 22504 Aborted <br>
>>> > > ./build_cc_ppc-linux_4.2.2_debug/test ><br>
>>> > > build_cc_ppc-linux_4.2.2_debug/test.log 2>&1<br>
>>> > > [tests/argmatch.c:127: Shorts]<br>
>>> > > [tests/argmatch.c:128: Longs]<br>
>>> > > [tests/argmatch.c:129: Combos]<br>
>>> > > [tests/argmatch.c:130: ShortsWithValues]<br>
>>> > > [tests/argmatch.c:131: LongsWithValues]<br>
>>> > > [tests/argmatch.c:132: MissingValue]<br>
>>> > > [tests/base.c:110: MemoryCheck]<br>
>>> > > [tests/base.c:111: EventBufferAdvance]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Invalid pointer to advance event buffer.<br>
>>> > > [tests/base.c:47]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:47]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Invalid pointer to advance event buffer.<br>
>>> > > [tests/base.c:56]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:56]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Tried to advance outside event buffer.<br>
>>> > > [tests/base.c:72]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:72]<br>
>>> > > [tests/base.c:112: EventBufferInvariant]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Event-buffer inconsistent (0x1080e008:11 !=<br>
>>> > > 0x1080e008:10). [tests/base.c:87]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:87]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Event-buffer inconsistent (0x1080e008:9 !=<br>
>>> > > 0x1080e008:10). [tests/base.c:91]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:91]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Event-buffer inconsistent (0x1080e009:10 !=<br>
>>> > > 0x1080e008:10). [tests/base.c:95]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:95]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Event-buffer inconsistent (0x1080e007:10 !=<br>
>>> > > 0x1080e008:10). [tests/base.c:99]<br>
>>> > > 2024-02-10,19:58:33:ERRR: Calling abort()... [tests/base.c:99]<br>
>>> > > [tests/bits.c:43: Gets]<br>
>>> > > [tests/bits.c:44: CountLoops]<br>
>>> > > [tests/caen_v1190.c:79: DefaultConfig]<br>
>>> > > 2024-02-10,19:58:33:INFO: Will try default cfg<br>
>>> > > path='/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg',<br>
>>> > > can be set with NURDLIB_DEF_PATH. [config/config.c:181]<br>
>>> > > 2024-02-10,19:58:33:INFO: Opened './tests/caen_v1190_empty.cfg' {<br>
>>> > > [config/parser.c:287]<br>
>>> > > 2024-02-10,19:58:33:ERRR: .Could not load default or user config<br>
>>> > > 'caen_v1190.cfg'. [config/config.c:1483]<br>
>>> > > 2024-02-10,19:58:33:ERRR: .Calling abort()... [config/config.c:1483]<br>
>>> > > make: *** [build_cc_ppc-linux_4.2.2_debug/test_ok] Error 1<br>
>>> > ><br>
>>> > ><br>
>>> > > Did you change anything in the GITLAB version between yesterday and 15<br>
>>> > > minutes ago?<br>
>>> > ><br>
>>> > ><br>
>>> > ><br>
>>> > > Sorry, sorry, sorry ��<br>
>>> > ><br>
>>> > ><br>
>>> > ><br>
>>> > ><br>
>>> > > Best greetings<br>
>>> > ><br>
>>> > > Günter<br>
>>> > ><br>
>>> > ><br>
>>> > ><br>
>>> > > P.S. Tomorrow or on Friday, I will set up a second DAQ system with<br>
>>> > > identical hardware. Then we can play around with no limits, including<br>
>>> > > flashing the firmware of the VULOM, without messing around with the<br>
>>> > > already running system as it is the case now.<br>
>>> > ><br>
>>> > ><br>
>>> > > ------------------------------------------------------------------------<br>
>>> > > *Von:* Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
>>> > > *Gesendet:* Mittwoch, 10. Januar 2024 16:59:07<br>
>>> > > *An:* Discuss use of Nurdlib, TRLO II, drasi and UCESB.; Weber, 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>
>>> > > Did you try to update r3bfuser? I cannot see this problem with new<br>
>>> > > versions of drasi+nurdlib+r3bfuser that are on Gitlab, and the trloii<br>
>>> > > version shouldn't matter much in this case.<br>
>>> > ><br>
>>> > > Cheers,<br>
>>> > ><br>
>>> > > Hans<br>
>>> > ><br>
>>> > > On 2024-01-10 16:54, Weber, Guenter Dr. wrote:<br>
>>> > >> Dear Håkan,<br>
>>> > >><br>
>>> > >><br>
>>> > >> I followed your suggestion and the result is this:<br>
>>> > >><br>
>>> > >><br>
>>> > >> RIO4-MCAL-2 mbsdaq > make drasi<br>
>>> > >> rm -f build_cc_ppc-linux_4.2.2_debug<br>
>>> > >> [ -d build_cc_ppc-linux_4.2.2_debug_drasi ] || mkdir -p<br>
>>> > >> build_cc_ppc-linux_4.2.2_debug_drasi<br>
>>> > >> ln -s build_cc_ppc-linux_4.2.2_debug_drasi<br>
>>> build_cc_ppc-linux_4.2.2_debug<br>
>>> > >> make -f Makefile.drasi<br>
>>> > >> make[1]: Entering directory<br>
>>> > >> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
>>> > >> CC build_cc_ppc-linux_4.2.2_debug/subevent.o<br>
>>> > >> In file included from ./subevent.h:11,<br>
>>> > >> from subevent.c:1:<br>
>>> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompa<br>
>>> t/<br>
>>> > s_veshe.h:16: error: expected specifier-qualifier-list before 'CHARS'<br>
>>> > >> make[1]: *** [build_cc_ppc-linux_4.2.2_debug/subevent.o] Error 1<br>
>>> > >> make[1]: Leaving directory<br>
>>> > >> `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
>>> > >> make: *** [drasi] Error 2<br>
>>> > >><br>
>>> > >><br>
>>> > >> Best greetings<br>
>>> > >><br>
>>> > >> Günter<br>
>>> > >><br>
>>> > >><br>
>>> > >><br>
>>> ------------------------------------------------------------------------<br>
>>> > >> *Von:* subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von<br>
>>> > >> Håkan T Johansson <f96hajo@chalmers.se><br>
>>> > >> *Gesendet:* Mittwoch, 10. Januar 2024 16:07:52<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>
>>> > >> those errors look strange to me. I am not able to reproduce on a<br>
>>> similar<br>
>>> > >> system.<br>
>>> > >><br>
>>> > >> As a workaround (to see how far we get), in subevent.h in the r3bfuser/<br>
>>> > >> directory, could you uncomment these:<br>
>>> > >><br>
>>> > >> #define MBS_TYPEDEFS_H<br>
>>> > >> typedef char CHARX;<br>
>>> > >> typedef int short INTS2;<br>
>>> > >> typedef int INTS4;<br>
>>> > >><br>
>>> > >> and comment out the "typedefs.h" in<br>
>>> > >><br>
>>> >>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscompa<br>
>>> t/<br>
>>> > s_veshe.h<br>
>>> > >><br>
>>> > >> on line 6. And then try again.<br>
>>> > >><br>
>>> > >> Cheers,<br>
>>> > >> Håkan<br>
>>> > >><br>
>>> > >><br>
>>> > >> On Wed, 10 Jan 2024, Weber, Guenter Dr. wrote:<br>
>>> > >><br>
>>> > >>><br>
>>> > >>> Dear Hans,<br>
>>> > >>><br>
>>> > >>><br>
>>> > >>> I now did rebuild NURDLIB and DRASI. Then I tried to compile R3BFUSER<br>
>>> > and this is the result:<br>
>>> > >>><br>
>>> > >>><br>
>>> > >>> RIO4-MCAL-2 mbsdaq > cd r3bfuser/<br>
>>> > >>> RIO4-MCAL-2 mbsdaq > make drasi<br>
>>> > >>> rm -f build_cc_ppc-linux_4.2.2_debug<br>
>>> > >>> [ -d build_cc_ppc-linux_4.2.2_debug_drasi ] || mkdir -p<br>
>>> > build_cc_ppc-linux_4.2.2_debug_drasi<br>
>>> > >>> ln -s build_cc_ppc-linux_4.2.2_debug_drasi<br>
>>> > build_cc_ppc-linux_4.2.2_debug<br>
>>> > >>> make -f Makefile.drasi<br>
>>> > >>> make[1]: Entering directory<br>
>>> > `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
>>> > >>> NCONF build_cc_ppc-linux_4.2.2_debug/nconf.args<br>
>>> > >>> UDP:ARPA_INET_H<br>
>>> > >>> CC build_cc_ppc-linux_4.2.2_debug/f_user.o<br>
>>> > >>> CC build_cc_ppc-linux_4.2.2_debug/subevent.o<br>
>>> > >>> In file includedfrom/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscom<br>
>>> pat/<br>
>>> > s_veshe.h:6,<br>
>>> > >>> from ./subevent.h:11,<br>
>>> > >>> from subevent.c:1:<br>
>>> >>>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscomp<br>
>>> at/<br>
>>> > typedefs.h:6: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTS8'<br>
>>> >>>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscomp<br>
>>> at/<br>
>>> > typedefs.h:7: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTU8'<br>
>>> >>>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscomp<br>
>>> at/<br>
>>> > typedefs.h:8: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTS4'<br>
>>> >>>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscomp<br>
>>> at/<br>
>>> > typedefs.h:9: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTU4'<br>
>>> >>>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscomp<br>
>>> at/<br>
>>> > typedefs.h:10: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTS2'<br>
>>> >>>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscomp<br>
>>> at/<br>
>>> > typedefs.h:11: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTU2'<br>
>>> >>>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscomp<br>
>>> at/<br>
>>> > typedefs.h:12: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTS1'<br>
>>> >>>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscomp<br>
>>> at/<br>
>>> > typedefs.h:13: error: expected '=', ',', ';', 'asm' or '__attribute__'<br>
>>> > before 'INTU1'<br>
>>> > >>> In file included from ./subevent.h:11,<br>
>>> > >>> from subevent.c:1:<br>
>>> >>>>/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/bin/../lwroc/../mbscomp<br>
>>> at/<br>
>>> > s_veshe.h:11: error: expected specifier-qualifier-list before 'INTS4'<br>
>>> > >>> subevent.c: In function 'begin_goosy_vme_subevent':<br>
>>> > >>> subevent.c:12: error: 's_veshe' has no member named 'l_dlen'<br>
>>> > >>> subevent.c: In function 'end_goosy_vme_subevent':<br>
>>> > >>> subevent.c:45: error: 's_veshe' has no member named 'l_dlen'<br>
>>> > >>> make[1]: *** [build_cc_ppc-linux_4.2.2_debug/subevent.o] Error 1<br>
>>> > >>> make[1]: Leaving directory<br>
>>> > `/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser'<br>
>>> > >>> make: *** [drasi] Error 2<br>
>>> > >>><br>
>>> > >>> Reminder: I am using the most recent versions of NURDLIB and DRASI,<br>
>>> but<br>
>>> > because of the incompatibility of the VULOM firmware I use the old version<br>
>>> > of TRLOII. In addition,<br>
>>> > >>> because of the leap seconds issue I compiled DRASI first on the PC and<br>
>>> > then recompiled it on the RIO (without "make clean").<br>
>>> > >>><br>
>>> > >>><br>
>>> > >>><br>
>>> > >>><br>
>>> > >>><br>
>>> > >>><br>
>>> > >>><br>
>>> > >>> Best greetings<br>
>>> > >>> Günter<br>
>>> > >>><br>
>>> > >>><br>
>>> >>>>________________________________________________________________________<br>
>>> ___<br>
>>> > __________________________________________________________________________<br>
>>> > _____________________<br>
>>> > >>> Von: Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
>>> > >>> Gesendet: Mittwoch, 10. Januar 2024 13:18:41<br>
>>> > >>> An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.; Weber, 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>
>>> > >>> I would suggest rebuilding nurdlib now that trlo2 has been rebuilt,<br>
>>> and<br>
>>> > >>> then also rebuild r3bfuser.<br>
>>> > >>><br>
>>> > >>> After that probably you can try to run the DAQ :)<br>
>>> > >>><br>
>>> > >>> Cheers,<br>
>>> > >>> Hans<br>
>>> > >>><br>
>>> > >>> On 2024-01-10 13:15, Weber, Guenter Dr. wrote:<br>
>>> > >>> > Dear Håkan,<br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > >>> > using the old TRLOII folder and then recompiling was successfull.<br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > >>> > Should I now give it a try to start the DAQ? Or is there something<br>
>>> > else<br>
>>> > >>> > I still need to adjust?<br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > >>> > Best greetings<br>
>>> > >>> ><br>
>>> > >>> > Günter<br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > ------------------------------------------------------------------------<br>
>>> > >>> > *Von:* subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag<br>
>>> > von<br>
>>> > >>> > Håkan T Johansson <f96hajo@chalmers.se><br>
>>> > >>> > *Gesendet:* Mittwoch, 10. Januar 2024 12:34:26<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>
>>> > >>> > Hi Günter,<br>
>>> > >>> ><br>
>>> > >>> > On Wed, 10 Jan 2024, Weber, Guenter Dr. wrote:<br>
>>> > >>> ><br>
>>> > >>> >><br>
>>> > >>> >> Hi folks,<br>
>>> > >>> >><br>
>>> > >>> >><br>
>>> > >>> >> the old "./find_firmware.pl" was working. This is the output:<br>
>>> > >>> >><br>
>>> > >>> >><br>
>>> > >>> >> a1729cda ../ver/rimfaxe0_trlo/rfx0_defs.h<br>
>>> > >>> >> 0866c243 ../ver/rimfaxe1_trlo/rfx1_defs.h<br>
>>> > >>> >> 5e8f5ef4 ../ver/tridi1_trlo/tridi_defs.h<br>
>>> > >>> >> 6e4ba1a9 ../ver/vulom4_trlo/trlo_defs.h<br>
>>> > >>> >> 68f8955e ../ver/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
>>> > >>> >> af33ed35 ../ver/vulom4_trlo_big/trlo_big_defs.h<br>
>>> > >>> >> 1409285e ../ver/vulom4b_trlo/trlo_defs.h<br>
>>> > >>> >> d374466d ../fw/tridi1_trlo/tridi_defs.h<br>
>>> > >>> >> d96ffc88 ../fw/vulom4_trlo/trlo_defs.h<br>
>>> > >>> >> 5b298165 ../fw/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
>>> > >>> >> 6f28c0f8 ../fw/vulom4_trlo_big/trlo_big_defs.h<br>
>>> > >>> >> fa5020ea ../fw/vulom4_trlo_led/trlo_defs.h<br>
>>> > >>> >> 426cb99c ../fw/vulom4b_trlo/trlo_defs.h<br>
>>> > >>> >> MKDIR fw_a1729cda_rfx0 # ../ver/rimfaxe0_trlo/rfx0_defs.h<br>
>>> > >>> >> SYMLINK fw_a1729cda_rfx0/rfx0_defs.h -><br>
>>> > ../../ver/rimfaxe0_trlo/rfx0_defs.h<br>
>>> > >>> >> MKDIR fw_0866c243_rfx1 # ../ver/rimfaxe1_trlo/rfx1_defs.h<br>
>>> > >>> >> SYMLINK fw_0866c243_rfx1/rfx1_defs.h -><br>
>>> > ../../ver/rimfaxe1_trlo/rfx1_defs.h<br>
>>> > >>> >> MKDIR fw_5e8f5ef4_tridi # ../ver/tridi1_trlo/tridi_defs.h<br>
>>> > >>> >> SYMLINK fw_5e8f5ef4_tridi/tridi_defs.h -><br>
>>> > ../../ver/tridi1_trlo/tridi_defs.h<br>
>>> > >>> >> MKDIR fw_6e4ba1a9_trlo # ../ver/vulom4_trlo/trlo_defs.h<br>
>>> > >>> >> SYMLINK fw_6e4ba1a9_trlo/trlo_defs.h -><br>
>>> > ../../ver/vulom4_trlo/trlo_defs.h<br>
>>> > >>> >> SYMLINK fw_1409285e_trlo -> fw_6e4ba1a9_trlo<br>
>>> > >>> >> MKDIR fw_68f8955e_trlo_all_in #<br>
>>> > ../ver/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
>>> > >>> >> SYMLINK fw_68f8955e_trlo_all_in/trlo_all_in_defs.h -><br>
>>> > ../../ver/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
>>> > >>> >> MKDIR fw_af33ed35_trlo_big #<br>
>>> > ../ver/vulom4_trlo_big/trlo_big_defs.h<br>
>>> > >>> >> SYMLINK fw_af33ed35_trlo_big/trlo_big_defs.h -><br>
>>> > ../../ver/vulom4_trlo_big/trlo_big_defs.h<br>
>>> > >>> >> MKDIR fw_d374466d_tridi # ../fw/tridi1_trlo/tridi_defs.h<br>
>>> > >>> >> SYMLINK fw_d374466d_tridi/tridi_defs.h -><br>
>>> > ../../fw/tridi1_trlo/tridi_defs.h<br>
>>> > >>> >> MKDIR fw_d96ffc88_trlo # ../fw/vulom4_trlo/trlo_defs.h<br>
>>> > >>> >> SYMLINK fw_d96ffc88_trlo/trlo_defs.h -><br>
>>> > ../../fw/vulom4_trlo/trlo_defs.h<br>
>>> > >>> >> SYMLINK fw_426cb99c_trlo -> fw_d96ffc88_trlo<br>
>>> > >>> >> SYMLINK fw_fa5020ea_trlo -> fw_d96ffc88_trlo<br>
>>> > >>> >> MKDIR fw_5b298165_trlo_all_in #<br>
>>> > ../fw/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
>>> > >>> >> SYMLINK fw_5b298165_trlo_all_in/trlo_all_in_defs.h -><br>
>>> > ../../fw/vulom4_trlo_all_in/trlo_all_in_defs.h<br>
>>> > >>> >> MKDIR fw_6f28c0f8_trlo_big #<br>
>>> ../fw/vulom4_trlo_big/trlo_big_defs.h<br>
>>> > >>> >> SYMLINK fw_6f28c0f8_trlo_big/trlo_big_defs.h -><br>
>>> > ../../fw/vulom4_trlo_big/trlo_big_defs.h<br>
>>> > >>> >><br>
>>> > >>> >> However, the compilation did end with an error:<br>
>>> > >>> >><br>
>>> > >>> >><br>
>>> > >>> >> make[1]: Enteringdirectory`/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl<br>
>>> /fw_d96ff<br>
>>> > c88_trlo'<br>
>>> > >>> >> CC bld_ppc-linux_4.2.2/src/trlo_check_version.o<br>
>>> > >>> >> CC bld_ppc-linux_4.2.2/src/trlo_functions.o<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c: In function 'trlo_clear_config':<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c:144: error: 'trlo_setup_map' has no<br>
>>> > member named 'sync_check_start_mux'<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c:146: error: 'trlo_setup_map' has no<br>
>>> > member named 'sync_check_stop_mux'<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c: In function 'trlo_print_config':<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c:825: error: 'trlo_setup_map' has no<br>
>>> > member named 'sync_check_start_mux'<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c:829: error: 'trlo_setup_map' has no<br>
>>> > member named 'sync_check_stop_mux'<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c: In function<br>
>>> > 'trlo_print_trig_status':<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c:1155: error: 'trlo_output_map' has<br>
>>> no<br>
>>> > member named 'trig_sync_check'<br>
>>> > >>> >> make[1]: *** [bld_ppc-linux_4.2.2/src/trlo_functions.o] Error 1<br>
>>> > >>> >> make[1]: Leavingdirectory`/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl<br>
>>> /fw_d96ff<br>
>>> > c88_trlo'<br>
>>> > >>> >><br>
>>> > >>> >> make[1]: Enteringdirectory`/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl<br>
>>> /fw_d3744<br>
>>> > 66d_tridi'<br>
>>> > >>> >> CC bld_ppc-linux_4.2.2/src/tridi_check_version.o<br>
>>> > >>> >> CC bld_ppc-linux_4.2.2/src/tridi_functions.o<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c: In function 'tridi_clear_config':<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c:144: error: 'tridi_setup_map' has<br>
>>> no<br>
>>> > member named 'sync_check_start_mux'<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c:146: error: 'tridi_setup_map' has<br>
>>> no<br>
>>> > member named 'sync_check_stop_mux'<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c: In function 'tridi_print_config':<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c:825: error: 'tridi_setup_map' has<br>
>>> no<br>
>>> > member named 'sync_check_start_mux'<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c:829: error: 'tridi_setup_map' has<br>
>>> no<br>
>>> > member named 'sync_check_stop_mux'<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c: In function<br>
>>> > 'tridi_print_trig_status':<br>
>>> > >>> >> ../trlolib/src/trlo_functions.c:1155: error: 'tridi_output_map' has<br>
>>> > no member named 'trig_sync_check'<br>
>>> > >>> >> make[1]: *** [bld_ppc-linux_4.2.2/src/tridi_functions.o] Error 1<br>
>>> > >>> >> make[1]: Leavingdirectory`/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/trloii/trloctrl<br>
>>> /fw_d3744<br>
>>> > 66d_tridi'<br>
>>> > >>> >> make: *** [fw_d374466d_tridi_build] Error 2<br>
>>> > >>> ><br>
>>> > >>> > That's what I feared. The new code want something (sync_check_...)<br>
>>> > not in<br>
>>> > >>> > the older firmware...<br>
>>> > >>> ><br>
>>> > >>> >> The fallback option is now to delete the new TRLOII folder and<br>
>>> > replace it with old one and then repeat the following steps?<br>
>>> > >>> >><br>
>>> > >>> >><br>
>>> > >>> >> cd trloii<br>
>>> > >>> >> make clean<br>
>>> > >>> >> make<br>
>>> > >>> >> cd trloctrl<br>
>>> > >>> >> make fw_d96ffc88_trlo_build<br>
>>> > >>> >> make fw_d374466d_tridi_build<br>
>>> > >>> >><br>
>>> > >>> >><br>
>>> > >>> >> Is this correct?<br>
>>> > >>> ><br>
>>> > >>> > Yes.<br>
>>> > >>> ><br>
>>> > >>> > There should then already be the trloii/fw/ directory, and the links<br>
>>> > that<br>
>>> > >>> > are created by find_firmware.pl<br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > >>> >> I also looked for the "--addr=" and this is the result:<br>
>>> > >>> ><br>
>>> > >>> >> ...<br>
>>> > >>> ><br>
>>> > >>> > Ok. I was too optimistic here. I looked through the grep results,<br>
>>> > but<br>
>>> > >>> > nothing obvious. Should be figurable by checking the old scripts<br>
>>> and<br>
>>> > >>> > following them around. Is a good way to see how things are done<br>
>>> > anyhow ;)<br>
>>> > >>> ><br>
>>> > >>> > Cheers,<br>
>>> > >>> > Håkan<br>
>>> > >>> ><br>
>>> > >>> ><br>
>>> > >>> >><br>
>>> > >>> >><br>
>>> > >>> >><br>
>>> > >>> >> Best greetings<br>
>>> > >>> >><br>
>>> > >>> >> Günter<br>
>>> > >>> ><br>
>>> > >>><br>
>>> > >>><br>
>>> > >><br>
>>> ><br>
>>> ><br>
>>> <br>
>>><br>
> <br>
</div>
</span></font>
</blockquote></div></body>
</html>