[last updated 18-September-2006] =============================================== Known problems for EPICS snc/seq version 2.0.11 =============================================== From: Eric Norum [mailto:norume _at_ aps.anl.gov] Sent: Monday, September 18, 2006 2:40 PM Subject: R3.14 sequencer Here's an entry for the 'known problems' file: Summary: Because of an interaction between the build rules and the C preprocessor sequencer programs which are preprocessed ('.st' files) must have %%#include changed to %%#include "vxWorks.h" Details: The R3.14 build rules invoke the C preprocessor with '-DvxWorks' for vxWorks targets. This will cause sequence program lines which refer to to be expanded to <1 .h>. This then causes errors when the compiler attempts to deal with these lines. ================================================================ Problem: From: Mark Rivers [mailto:rivers _at_ cars.uchicago.edu] Sent: Tuesday, April 18, 2006 3:12 PM Subject: Problems with files in seq-2-0-11/configure Folks, I am having problems building seq 2-0-11 for win32-x86. In all other modules if I create a file called RELEASE.win32-x86 it uses that file to define the locations of other modules, including base. However, if I do this in the latest version of seq, it does not work. It appears to be using RELEASE, not RELEASE.win32-x86. Solution: From: Janet Anderson [mailto:jba_at_aps.anl.gov] Sent: Wednesday, April 19, 2006 11:47 AM Subject: Re: Problems with files in seq-2-0-11/configure The following fix is needed for seq version 2-0-11 only. Rename your RELEASE. file to RELEASE..Common or, if you prefer, make the following changes to the configure/CONFIG file: Index: CONFIG =================================================================== RCS file: /usr/local/epicsmgr/cvsroot/epics/modules/soft/seq/configure/CONFIG,v retrieving revision 1.11 diff -r1.11 CONFIG 3a4 > -include $(TOP)/configure/RELEASE.$(EPICS_HOST_ARCH) 17a19 > -include $(TOP)/configure/CONFIG_SITE.$(EPICS_HOST_ARCH) Janet [end]