Hi EPICS folks,
When trying to compile base 3.14.12.1 on my Cygwin installation on
WinXp (32 bit), I got the error message about parse.c (attached at the end).
It is fairly similar to what Kaz described late last year in this thread--
http://www.aps.anl.gov/epics/tech-talk/2010/msg02120.php
However, in my case, I am not compiling for win32-x86 but for
cygwin-x86. There should be no '\\' problem for the paths. I also checked
the file permission and my antelope.exe file is executable, both in
Windows-native and Cygwin environment. Similar to Kaz's experience, I had
no problem compiling 3.14.11. I am using Gnumake 3.8.1 coming with my
Cygwin installation, though I am not sure hold old my cygwin is. I kind of
remember that compiling 3.14.8.2 for win32-x86, I had to use 3.8.0 to deal
with the '\\' problem. But I just don't know how to get make-3.8.0 to work
with 3.14.12, because in RULES.TARGET, there is comments about 3.8.1 and
later only. I could not get pass that with 3.8.0. For now, I will stick
with 3.14.11. But I just wonder what could cause my problem.
Thanks!
Here goes the error message (between ****)--
**********************************
$ make
make -C ./configure install
make[1]: Entering directory `/usr/local/base-3.14.12.1/configure'
make -C O.cygwin-x86 -f ../Makefile TOP=../.. T_A=cygwin-x86 install
make[2]: Entering directory
`/usr/local/base-3.14.12.1/configure/O.cygwin-x86'
make[2]: Nothing to be done for `install'.
make[2]: Leaving directory
`/usr/local/base-3.14.12.1/configure/O.cygwin-x86'
make[1]: Leaving directory `/usr/local/base-3.14.12.1/configure'
make -C ./src install
make[1]: Entering directory `/usr/local/base-3.14.12.1/src'
make -C ./tools install
make[2]: Entering directory `/usr/local/base-3.14.12.1/src/tools'
make -C O.cygwin-x86 -f ../Makefile TOP=../../.. T_A=cygwin-x86 install
make[3]: Entering directory
`/usr/local/base-3.14.12.1/src/tools/O.cygwin-x86'
make[3]: Nothing to be done for `install'.
make[3]: Leaving directory
`/usr/local/base-3.14.12.1/src/tools/O.cygwin-x86'
make[2]: Leaving directory `/usr/local/base-3.14.12.1/src/tools'
make -C ./makeBaseApp install
make[2]: Entering directory `/usr/local/base-3.14.12.1/src/makeBaseApp'
make -C O.cygwin-x86 -f ../Makefile TOP=../../.. T_A=cygwin-x86 install
make[3]: Entering directory
`/usr/local/base-3.14.12.1/src/makeBaseApp/O.cygwin-x86'
make[3]: Nothing to be done for `install'.
make[3]: Leaving directory
`/usr/local/base-3.14.12.1/src/makeBaseApp/O.cygwin-x86'
make[2]: Leaving directory `/usr/local/base-3.14.12.1/src/makeBaseApp'
make -C ./makeBaseExt install
make[2]: Entering directory `/usr/local/base-3.14.12.1/src/makeBaseExt'
make -C O.cygwin-x86 -f ../Makefile TOP=../../.. T_A=cygwin-x86 install
make[3]: Entering directory
`/usr/local/base-3.14.12.1/src/makeBaseExt/O.cygwin-x86'
make[3]: Nothing to be done for `install'.
make[3]: Leaving directory
`/usr/local/base-3.14.12.1/src/makeBaseExt/O.cygwin-x86'
make[2]: Leaving directory `/usr/local/base-3.14.12.1/src/makeBaseExt'
make -C ./libCom install
make[2]: Entering directory `/usr/local/base-3.14.12.1/src/libCom'
make -C O.cygwin-x86 -f ../Makefile TOP=../../.. T_A=cygwin-x86 install
make[3]: Entering directory
`/usr/local/base-3.14.12.1/src/libCom/O.cygwin-x86'
make[3]: Nothing to be done for `install'.
make[3]: Leaving directory
`/usr/local/base-3.14.12.1/src/libCom/O.cygwin-x86'
make[2]: Leaving directory `/usr/local/base-3.14.12.1/src/libCom'
make -C ./toolsComm install
make[2]: Entering directory `/usr/local/base-3.14.12.1/src/toolsComm'
make -C ./antelope install
make[3]: Entering directory
`/usr/local/base-3.14.12.1/src/toolsComm/antelope'
make -C O.cygwin-x86 -f ../Makefile TOP=../../../.. T_A=cygwin-x86 install
make[4]: Entering directory
`/usr/local/base-3.14.12.1/src/toolsComm/antelope/O.cygwin-x86'
make[4]: Nothing to be done for `install'.
make[4]: Leaving directory
`/usr/local/base-3.14.12.1/src/toolsComm/antelope/O.cygwin-x86'
make[3]: Leaving directory
`/usr/local/base-3.14.12.1/src/toolsComm/antelope'
make -C ./flex install
make[3]: Entering directory `/usr/local/base-3.14.12.1/src/toolsComm/flex'
make -C O.cygwin-x86 -f ../Makefile TOP=../../../.. T_A=cygwin-x86 install
make[4]: Entering directory
`/usr/local/base-3.14.12.1/src/toolsComm/flex/O.cygwin-x86'
rm -f parse.c y.tab.c
rm -f parse.h y.tab.h
../../../../bin/cygwin-x86/antelope.exe -l -d ../parse.y
make[4]: *** [parse.c] Error 34
make[4]: Leaving directory
`/usr/local/base-3.14.12.1/src/toolsComm/flex/O.cygwin-x86'
make[3]: *** [install.cygwin-x86] Error 2
make[3]: Leaving directory `/usr/local/base-3.14.12.1/src/toolsComm/flex'
make[2]: *** [flex.install] Error 2
make[2]: Leaving directory `/usr/local/base-3.14.12.1/src/toolsComm'
make[1]: *** [toolsComm.install] Error 2
make[1]: Leaving directory `/usr/local/base-3.14.12.1/src'
make: *** [src.install] Error 2
**************************************
---------------------------------
Zhan Zhang, Ph. D.
Argonne National Laboratory
X-ray Science Division, 438-D005
9700 S. Cass Ave.
Argonne, IL 60439
Tel : 630-252-0863
Email: [email protected]
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Kevin Tsubota
Sent: Friday, May 20, 2011 1:11 PM
To: Dirk Zimoch
Cc: [email protected]
Subject: RE: problem with gateway and softIoc running on same server
Thank you very much Dirk.
I'm not sure what was going on but I used the -cip localhost:8164 and
everything started working as expected. I went back to specifying the
IP and things still worked as expected.
Maybe I just needed the day off :-)
Thanks again!
Kevin
-----Original Message-----
From: Dirk Zimoch [mailto:[email protected]]
Sent: Wednesday, May 18, 2011 11:31 PM
To: Kevin Tsubota
Cc: [email protected]
Subject: Re: problem with gateway and softIoc running on same server
Hello Kevin,
When you run two or more CA servers (IOCs or gateways) on the same
machine, you cannot reach all of them with the host ip address in
EPICS_CA_ADDR_LIST. You can only reach all with the broadcast address.
Thats exactly what the warning that an IOC prints in this case is about:
cas warning: Configured TCP port was unavailable.
cas warning: Using dynamically assigned TCP port 38724,
cas warning: but now two or more servers share the same UDP port.
cas warning: Depending on your IP kernel this server may not be
cas warning: reachable with UDP unicast (a host's IP in
EPICS_CA_ADDR_LIST)
However, it should work when using different ports for the IOC and the
gateway server part. I tried it:
(on the same host)
export EPICS_CA_SERVER_PORT=8164
<start the ioc with ai record DZ-ai:ch1>
unset EPICS_CA_SERVER_PORT
gateway -cip 129.129.145.26:8164 -sip 129.129.145.26 -sport 5064
caget DZ-ai:ch1
DZ-ai:ch1 0
Works.
gateway -cip localhost:8164 -sip 129.129.145.26 -sport 5064
Works too.
Maybe using localhost is the solution for you.
Also check the firewall settings.
sudo /sbin/iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
(No filtering here)
Best regards,
Dirk
Kevin Tsubota wrote:
Hi,
I want a gateway to publish PVs from 192.168.134.51:8064 which is on a
private network connected to 192.171.95.112 (where a softIoc is
already
running) because I can't access this private
I have the situation where I have a solaris-8 server (192.171.95.112)
with two network cards. One goes to our observatory network and the
other goes to a private network running a windows based softIoc
(192.168.134.51). Now I need access to the PVs of the widows softIoc
from other IPs on the observatory network.
I can successfully get the gateway to publish the windows softIoc PVs
without any problems. However, I have a solaris softIoc running on
the
same server as the gateway and this is where I'm having problems. I've
tried using different EPICS_CA_SERVER_PORTS for both IOCs but no
matter
what I try I can't get the gateway to see the solaris IOC on the same
IP. If I manually set my EPICS_CA_SERVER_PORT at the command line
then
issue a caget, it successfully returns the PV value but it reports
that
there's multiple instances of the PV.
My question is: can a gateway co-exist with a softIoc in the same ip
address?
If so, what do I need to do to make it happen? Using different
EPICS_CA_SERVER_PORTs doesn't seem to be it. Is this related to the
fact that I can't run multiple softIocs on the same server unless I
change port numbers? In which case I'd want a gateway to interface to
them as well.
Here's my startup command run on the solaris server (128.171.95.112):
/usr/local/epics/r3.14.9/extensions/bin/solaris-sparc-gnu/gateway
-debug
1 -pvlist k1lmct.pvlist -access GATEWAY.access -home $HOME -log
k1lmct.log -sip "128.171.95.112" -sport 5064 -cip "192.171.95.112:8164
192.168.134.51:8064" -prefix k1:lmct:gateway&
Here's the start of the debug output log:
PV Gateway Version 2.0.3.0 [Feb 20 2008 16:27:23]
EPICS 3.14.9 PID=13539
EPICS_CA_ADDR_LIST=192.171.95.112:8164 192.168.134.51:8064
EPICS_CA_AUTO_ADDR_LIST=NO
EPICS_CA_SERVER_PORT=Not specified
EPICS_CA_MAX_ARRAY_BYTES=Not specified
EPICS_CAS_INTF_ADDR_LIST=128.171.95.112
EPICS_CAS_SERVER_PORT=5064
EPICS_CAS_IGNORE_ADDR_LIST=Not specified
Thank you in advance!
Kevin Tsubota
W.M. Keck Observatory
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·