Experimental Physics and
Industrial Control System

From: Johnson, Andrew N. <anj at anl.gov>
Sent: 24 August 2021 18:13
To: Jones, Edward (CODAS&IT) <edward.jones1 at ukaea.uk>
Cc: EPICS tech-talk <tech-talk at aps.anl.gov>
Subject: Re: LIB_LIBS getting ignored

 

I’m trying to run a build where we’ve set INSTALL_LOCATION to /prefix and have found a buildable form with:

make EPICS_BASE=/prefix SUPPORT=/prefix

However, when I try to build my IOC itself at the final hurdle it doesn’t seem to link anything. This is what it tries to link:

 

/usr/bin/x86_64-w64-mingw32-g++ -o PICamApp.exe -static -L/ADPICam/lib/windows-x64-mingw -L/ADPICam/iocs/PICamIOC/lib/windows-x64-mingw       -m64    -static-libgcc -static-libstdc++         PICamApp_registerRecordDeviceDriver.o PICamAppMain.o    -lADPICam -lPicam  -lnetapi32    -lpsapi -lws2_32 -ladvapi32 -luser32 -lkernel32 -lwinmm -ldbghelp

 

Which lacks all the EPICS_BASE_IOC_LIBS, when I manually navigate to that directory and link it like so:

 

/usr/bin/x86_64-w64-mingw32-g++ -o PICamApp.exe -static -L/ADPICam/lib/windows-x64-mingw -L/ADPICam/iocs/PICamIOC/lib/windows-x64-mingw -L/prefix/lib/windows-x64-mingw      -m64    -static-libgcc -static-libstdc++         PICamApp_registerRecordDeviceDriver.o PICamAppMain.o    -lADPICam -lPicam  -lnetapi32    -lpsapi -lws2_32 -ladvapi32 -luser32 -lkernel32 -lwinmm -ldbghelp -ldbRecStd -ldbCore -lca -lCom -lasyn -lADBase -lca -lCom -lxml2 -lgdi32 -loleaut32 -lwsock32 -lws2_32 -lpsapi -ldbghelp -lversion -lzlib -lpv -ladvapi32 -luser32

   

This works. So it looks like the build method is missing all LIB_LIBS definitions. Could someone help to understand this? If you need I can share our work but must be privately done.

I’m the lead maintainer for the build system but I don’t have time to look into any details this week. I’m pretty sure the above should solve it, but if not you might also get some input from others too as long as you respond back to the list and not just to me privately. It often helps to post parts of your Makefiles if they’re your own or you have made changes to them, or pointers to online copies if they are unmodified from published support modules. We shouldn’t have to see any private code to help fix this.

- Andrew