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