Experimental Physics and
| |||||||||||||||
|
See thread: http://www.aps.anl.gov/epics/tech-talk/2009/msg01132.php It turned out that I was building on a Xeon 3040 dual core machine and I had to apply a patch described in the R3.14.10 "Known Problems" documentation. "IOCs or other EPICS programs running on a Win32 system with multiple CPUs may die at startup. This problem can also cause some of the EPICS build tools to die and for the build to fail (any of these programs could cause this: aitGen, antelope, dbToMenuH, dbToRecordtypeH, e_flex, genApps, makeBpt). This patch applied to the base/src/libCom/osi/os/WIN32/osdTime.cpp file solves an issue with time provider registration on Windows." Everything was fine until last week when this Xeon based PC died. Our computer group replaced it with a nominally identical spare - but it turns out that this spare has "Pentium Dual CPU", E2180 instead of the Xeon. On this replacement I cannot get EPICS to build with or without the patch. Base might build, but then as I tried to build various products, e.g. asyn or autosave, I would eventually run into an "unresolved symbols" error where there shouldn't be one. This is the same type of error I originally came across back in August< seem to be independent of compiler choice - Microsoft, MinGW Just for fun I also tried R3.14.11 on the "Pentium Dual CPU" E2180 without success. At the moment I am trying to replicate the build on another Xeon machine but I am befuddled by this whole issue. Normally I wouldn't think twice about the particular CPU model I am using. Any advice? John Dobbins
| ||||||||||||||
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |