RE: Building 3.14.1 under cygwin environment

["Redman, Russell O." <Russell.Redman@nrc-cnrc.gc.ca>]

Dear Eric,

I got EPICS R3.13.4 running under Cygwin with WinNT, but was warned that the
Cygwin thread library was not adequate for R3.14.  I have attached Janet
Anderson's reply on the subject from 2001-02-06.  Many things may have
changed since then, of course!

Dr. Russell O. Redman
Tel: (250) 363-6917 | Fax: (250) 363-0045
<mailto:Russell.Redman@nrc-cnrc.gc.ca>
National Research Council Canada | Conseil national de recherches Canada
5071 West Saanich Road           | 5071 West Saanich Road
Victoria, B. C. V9E 2E7          | Victoria, C.-B. V9E 2E7
Government of Canada             | Gouvernement du Canada

> -----Original Message-----
> From: Chris Mayer [mailto:cjm@observatorysciences.co.uk]
> Sent: Monday, 2003 April 28 4:25 AM
> To: Eric Norum
> Cc: tech-talk@aps.anl.gov
> Subject: Re: Building 3.14.1 under cygwin environment
> 
> 
> Eric Norum wrote:
> 
> > What I usually do in situations like this is to issue the compile
> > command with -c changed to -E so I can see exactly what's 
> getting passed
> >   on from the preprocessor to the compiler.  The offending line is:
> >      fd_set fdSets[fdrNEnums];
> > This makes me think that the likely cause of the problem is that
> > 1) fd_set is not typefed properly.  (to check, run the output of the
> > '-E' compile through 'grep fd_set'.
> > OR
> > 2) fdSets is being defined as a preprocessor macro somewhere in some
> > cygwin header file.  About the only thing to do here is to 
> 'grep fdSets'
> > on all the header files.
> > 
> > BTW -- is EPICS likely to work on win98???
> > 
> 
>   Thanks for the tips I'll give that a try. Does anyone know 
> the answer
> to Eric's question about win98 ? This is my first foray into running
> Epics/Channel Access from a Windows environment so any help would be
> appreciated. Also, does anyone know what the situation is with XP ?
> 
>       Chris Mayer
> ______________________________________________________________
> _________
> Observatory Sciences Ltd.          Email: 
> cjm@observatorysciences.co.uk
> William James House                Tel: 44 - (0)1223 - 508257
> Cowley Road,                       Fax: 44 - (0)1223 - 508258
> Cambridge, CB4 0WX, UK             
> http://www.observatorysciences.co.uk
>

--- Begin Message ---

Subject:	Re: FW: Building EPICS under Cygwin32
From:	Janet Anderson <jba@aps.anl.gov>
To:	"Redman, Russell O." <Russell.Redman@nrc-cnrc.gc.ca>
Date:	Tue, 6 Feb 2001 11:56:16 -0700

"Redman, Russell O." wrote:
> 
> Dear Janet,
> 
> Kay-Uwe points out that you are the build system expert, and may have an
> interest in this.  I have just succeeded (I think) in building EPICS under
> the latest-but-one release of Cygwin.  My biggest single concern is the
lack
> of support for point-to-point TCP/IP connections under Cygwin - I
> conditionally commented out the offending lines, but have absolutely no
idea
> what the consequences of this will be.
> 
> Is there a way to exercise the system to verify that it behaves correctly
> [preferably without doing a lot of additional work ;-)]?
> 

Did you try building some host tools (medm, alh, camonitor, ...) which use
the base libraries to see if they work. You could build an EPICS application
for a vxWorks target, load the application into vxWorks and then monitor
the pvs with camonitor or medm to see if they are processing properly and
that channel access is working. We do not have a test module to send you.

Which version of EPICS are you building? I don't remember R3.13.4 using
TOUCH.
Thank you for sending me your blow-by-blow description of the build. I 
will look at it closely and try to fix the problems in R3.13 
(LINK.cc and others ????). C++ is required for R3.14 base.

In R3.14 all build created files, even db and dbd files, are created
in an O. subdirectory and almost all alpha1 references to TOUCH have been 
removed. Only one reference remains in alpha2 RULES.Db and that rule 
may no longer be needed. I would like to get a copy of e2db. We do
not use it here. I could then look into your e2db build problems
and I could try it out with the new R3.14 config file changes. 

I use the cygwin tools all the time on my NT and I use the cygwin make for
all my win32 builds with MS Visual c++ and the borland c++ compiler but I
rarely use the cygwin bash shell. Cygwin make has no problems with the
directory specifications /name/name, C:\\name\\name, and C:/name/name.
Why are you using the Tornado make?

I had planned to support the cygwin compiler and even added cygwin config
files for a few versions of R3.13.  But it seems that the cygwin compiler
does not support posix threads (or any threads) and thread support is
required for EPICS R3.14. This was true for cygwin 1.1.2 when I tried
using it last year and I have not heard that thread support is available
in the latest release. I will add EPICS support for cygwin in R3.14 when
threads are supported in cygwin.

EPICS base R3.13.3 and R3.13.4 do have support for the Borland win32
c++ compiler. bcc32. It may be easier for you to download and use this
free compiler with cygwin make instead of hacking base to use the
current cygwin compiler. 

Hope this helps.

Janet



>

--- End Message ---