Experimental Physics and
Industrial Control System

Freddie Akeroyd - STFC UKRI via Tech-talk <tech-talk at aps.anl.gov> · Sat, 17 Apr 2021 22:09:40 +0000

Hi Marty,

It looks like at some point I created a "linux-x86_64-static" EPICS host arch config on our system that set:

STATIC_BUILD = YES
SHARED_LIBRARIES = NO

I think that the default EPICS linux build creates both shared and archive libraries, but the shared ones may get preferred over archive libraries during linking.

There are two travis windows builds, one for DLL linking and one for static linking. I see that the windows build is actually a MinGW/Wine cross compile on Ubuntu - I think some of the library order issues you are seeing may be an artefact of this. I believe the linux static linker only makes one pass, but the windows linker always make multiple passes, so you may see issues with the cross compile that would not occur on native windows - however I think they would still occur when linking statically for a linux target  

Regards,

Freddie

> -----Original Message-----
> From: Marty Kraimer <mrkraimer at comcast.net>
> Sent: 17 April 2021 22:34
> To: Akeroyd, Freddie (STFC,RAL,ISIS) <freddie.akeroyd at stfc.ac.uk>
> Cc: tech talk <tech-talk at aps.anl.gov>
> Subject: Re: WIN_32
> 
> On 4/17/21 4:54 PM, Freddie Akeroyd - STFC UKRI wrote:
> > Hi Marty,
> >
> > Do you also build your programs linked statically on linux too? If
> > not, it might be worth doing that too - I believe any purely link
> > order issues you may see with travis windows should also occur when
> > linking statically on linux
> >
> > Regards,
> >
> > Freddie
> 
> How do I do this on Linux?
> 
> I also have a couple of questions about the travis  builds.
> 1) Why are there two sets of builds,
> 2) Do  any of the gcc or clang builds statically linked.
> 
> Marty
> >
> >> -----Original Message-----
> >> From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Mark
> >> Rivers via Tech-talk
> >> Sent: 17 April 2021 13:37
> >> To: Marty Kraimer <mrkraimer at comcast.net>
> >> Cc: EPICS Tech-Talk <tech-talk at aps.anl.gov>
> >> Subject: Re: WIN_32
> >>
> >> Hi Marty,
> >>
> >>
> >> You are making progress, the error is now different:
> >>
> >>
> >> /home/travis/.source/pvaClient/lib/linux-x86_64/libpvaClient.a(pvaCli
> >> ent.o): In function `epics::pvaClient::PvaClient::~PvaClient()':
> >> /home/travis/.source/pvaClient/src/O.linux-x86_64/../pvaClient.cpp:156:
> >> undefined reference to `epics::pvAccess::ClientFactory::stop()'
> >>
> >> So now a function in pvaClient is not finding the pvAccess functions.
> >> That is probably a link order problem.
> >>
> >> Try this:
> >>
> >>
> >> EPICS_BASE_PVA_CORE_LIBS =  pvaClient  pvDatabase pvAccess pvAccessCA
> >> pvData Com
> >>
> >> Or leave EPICS_BASE_PVA_CORE_LIBS as it was originally and add
> >> pvaClient
> >> here:
> >>
> >> PROD_HOST += serviceMain
> >> serviceMain_SRCS += serviceMain.cpp
> >> serviceMain_LIBS += controlRecord
> >> serviceMain_LIBS += powerSupplyRecord serviceMain_LIBS += linkRecord
> >> serviceMain_LIBS += pvaClient serviceMain_LIBS +=
> >> $(EPICS_BASE_PVA_CORE_LIBS)
> >>
> >> Mark
> >>
> >>
> >> ________________________________
> >> From: Marty Kraimer <mrkraimer at comcast.net>
> >> Sent: Saturday, April 17, 2021 7:07 AM
> >> To: Mark Rivers
> >> Cc: EPICS Tech-Talk
> >> Subject: Re: WIN_32
> >>
> >> On 4/16/21 5:44 PM, Mark Rivers wrote:
> >>> EPICS_BASE_PVA_CORE_LIBS = pvDatabase pvAccess pvAccessCA pvData
> >> pvaClient Com
> >> Mark,
> >>
> >> I made that change.
> >> The pull request still fails for windows and rtems.
> >>
> >> Does it build for You on windows?
> >>
> >> Marty
> > This email and any attachments are intended solely for the use of the named
> recipients. If you are not the intended recipient you must not use, disclose,
> copy or distribute this email or any of its attachments and should notify the
> sender immediately and delete this email from your system. UK Research and
> Innovation (UKRI) has taken every reasonable precaution to minimise risk of
> this email or any attachments containing viruses or malware but the recipient
> should carry out its own virus and malware checks before opening the
> attachments. UKRI does not accept any liability for any losses or damages
> which the recipient may sustain due to presence of any viruses. Opinions,
> conclusions or other information in this message and attachments that are not
> related directly to UKRI business are solely those of the author and do not
> represent the views of UKRI.
> >

This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System