1994 1995 1996 1997 1998 1999 2000 2001 2002 <2003> 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 <2003> 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: EPICS Sequencer v.2.0.4 on EPICS base v.3.14.1 |
From: | Kukhee Kim <[email protected]> |
To: | "'Chestnut, Ronald P.'" <[email protected]>, [email protected], [email protected], "'Laznovsky, Michael'" <[email protected]> |
Cc: | [email protected] |
Date: | Tue, 10 Jun 2003 21:38:40 -0700 |
Misaki-san;
I think that the seq-2.0.2 is best choice for R3.14.1. You can modify just one line to compile seq-2.0.2 with R3.14.1. Please edit seq-2.0.2/src/seq/seq-qry.c and insert (ELLNODE *) on line 275. 275c275 < pEntry = (QENTRY *) ellNext((pEntry), i++) --- > pEntry = (QENTRY *) ellNext((ELLNODE *)pEntry), i++)
If you want to use seq-2.0.4 with R3.14.1, it is also possible. But you have to make small change on seq-2.0.4/src/dev/devSequencer.c file. You can comment out following lines to compile seq-2.0.4 with R3.14.1. Those lines correspond to new feature of R3.14.2, so we don’t need it on R3.14.1.
/* #include epicsExport.h */
/* LOCAL DSET devSiSeq = { 5, NULL, NULL, siInit, NULL, siRead }; epicsExportAddress(dset,devSiSeq); */
I just tested compiling seq-2.0.4 with R3.14.1. Following is the initializing message from my IOC. ############################################################################ ### EPICS IOC CORE built on Mar 21 2003 ### EPICS R3.14.1 $R3-14-1$ $2002/12/12 15:56:59$ ############################################################################ Starting iocInit khkimHost:subExample mySubInit process 0x8061070 seq sncExample,"user=khkimHost" @(#)SEQ Version 2.0.4: Tue Jun 10 18:12:40 PDT 2003 iocInit: All initialization complete Spawning state program "sncExample", thread 0x80ed6b0: "sncExample" epics> seqShow Program Name Thread ID Thread Name SS Name
sncExample 0x80ed6b0 sncExample ss1
epics>
I hope, it can help you. Thank you.
/Kukhee
June 10, 2003 -- Kuk-Hee Kim ESD, Software Engineering (ESD/18E) Technical Division Stanford Linear Accelerator Center 2575 Sand Hill Road, MS46, Menlo Park, CA 94025 E-mail: [email protected] Tel: +1 (650) 926 2497, Fax: +1 (650) 926 3515 Home: +1 (408) 720 8261
-----Original Message-----
Misaki-san,
One of our software engineers has done exactly what you are asking about. I will ask Kukhee Kim to answer separately. I am also sending a separate E-mail with Kukhee's comments to Marty on his experience building the 2.0.4 sequencer.
/Ron Chestnut
-----Original Message----- From: Misaki (KOBAYASHI) KOMIYAMA [mailto:[email protected]] Sent: Tuesday, June 10, 2003 5:57 PM Subject: EPICS Sequencer v.2.0.4 on EPICS base v.3.14.1
Dear All,
Hello.
I'm sorry to trouble you, but I have a question. Can I use the EPICS Sequencer v.2.0.4 on the EPICS base v.3.14.1? I have a Linux (Redhat8) machine which includes EPICS base v.3.14.1. When I tried to install the v.2.0.4-sequencer programs on it as following the guide in the EPICS Sequencer home page, I failed. The error message said that devSequencer.c" could not find "epicsExport.h".
On the other hand, when I tried to install the v.2.0.2-sequencer programs on the Linux machine, I also failed in compiling the programs. The error message was appeared, which was reported in the sequencer home page; "structure has no member named 'next'. I tried to find the v.2.0.3-programs, but I could not find it.
Now, I cannot install EPICS Sequencer in my machine. May I ask you some helps to me?
Best Regards, Misaki KOMIYAMA (RIKEN, JAPAN) |