g+
g+ Communities
Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014 
<== Date ==> <== Thread ==>

Subject: Windows busy build error - epics 3.14.12.1
From: Emma Shepherd <Emma.Shepherd@synchrotron.org.au>
To: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Fri, 20 Apr 2012 11:15:17 +1000
Hi folks,

Banging my head against a Windows build error...

I'm trying to get to the stage where I can build AreaDetector 1-7 on 64-bit Windows 7.  I can successfully build base-13-12-1 and asyn-4-18, but my first hurdle is that busy 1-4 fails with the following link error:

Creating library busy.lib and object busy.exp
devBusyAsyn.obj : error LNK2001: unresolved external symbol pasynEpicsUtils
devBusyAsyn.obj : error LNK2001: unresolved external symbol pasynInt32SyncIO
devBusyAsyn.obj : error LNK2001: unresolved external symbol pasynManager
devBusyAsyn.obj : error LNK2001: unresolved external symbol pasynTrace
busy.dll : fatal error LNK1120: 4 unresolved externals
make[3]: *** [busy.dll] Error 1120
make[3]: Leaving directory `C:/beamline/perforce/Dev/SBS/4_Controls/4_3_Network_Infrastructure/4_3_1_Comms_Common_Services/sw/epics/busy-1-4/busyApp/src/O.windows-x64'
make[2]: *** [install.windows-x64] Error 2
make[2]: Leaving directory `C:/beamline/perforce/Dev/SBS/4_Controls/4_3_Network_Infrastructure/4_3_1_Comms_Common_Services/sw/epics/busy-1-4/busyApp/src'
make[1]: *** [src.install] Error 2
make[1]: Leaving directory `C:/beamline/perforce/Dev/SBS/4_Controls/4_3_Network_Infrastructure/4_3_1_Comms_Common_Services/sw/epics/busy-1-4/busyApp'
make: *** [busyApp.install] Error 2


I'm using Visual Studio 2010, and gnumake.  The problem seems to be with the version of EPICS base, as I get the same problem when I try to compile it as 32-bit as well unless I revert to EPICS 3.14.11.  I can build other modules that depend on asyn just fine (like std).

Any ideas?

Thanks,
Emma
<br>This message and any attachments may contain proprietary or confidential information. If you are not the intended recipient or you received the message in error, you must not use, copy or distribute the message. Please notify the sender immediately and destroy the original message. Thank you.

Replies:
RE: Windows busy build error - epics 3.14.12.1 Mark Rivers

Navigate by Date:
Prev: asyn training at the EPICS Collaboration Meeting next week Mark Rivers
Next: How to apply for Java SWT DateTime widget in CSS OPI? [SEC=UNCLASSIFIED] WANG, Jian
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014 
Navigate by Thread:
Prev: asyn training at the EPICS Collaboration Meeting next week Mark Rivers
Next: RE: Windows busy build error - epics 3.14.12.1 Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·