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 How-To , Installation on Windows |
From: | John Dobbins via Tech-talk <tech-talk at aps.anl.gov> |
To: | "Akeroyd, Freddie (STFC,RAL,ISIS)" <freddie.akeroyd at stfc.ac.uk>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Mon, 2 Nov 2020 22:23:41 +0000 |
Thanks, I just discovered that the older version I grabbed from gnuwin32 (re2c 0.9.4) doesn't work.
John
From: Akeroyd, Freddie (STFC,RAL,ISIS) <freddie.akeroyd at stfc.ac.uk>
Sent: Monday, November 2, 2020 5:17 PM To: John Dobbins <john.dobbins at cornell.edu>; tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: RE: EPICS How-To , Installation on Windows Hi John,
There are some options for re2c on windows listed at https://www-csr.bessy.de/control/SoftDist/sequencer/Installation.html
Regards,
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of John Dobbins via Tech-talk
I have switched to Visual Studio Community Editon + Strawberry PERL. I was able to build base 3.15.8 without error.
Is there a recommended way to get re2c on Windows?
John
From: Engbretson, Mark S. <engbretson at anl.gov>
2019 has worked fine since it came out . . .
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Mark Rivers via Tech-talk
I believe Community Edition 2019 works fine, though I have only tested up to 2017. And Strawberry Perl will give you perl and gnumake.
Mark
From: John Dobbins <john.dobbins at cornell.edu>
Mark,
"I think most Windows users are using Visual Studio and not mingw."
Good to know. Looking at various pages it wasn't clear what practice is common these days.
Is Community Edition 2019 known to work? This plus Strawberry PERL?
John
From: Mark Rivers <rivers at cars.uchicago.edu>
Hi John,
I think most Windows users are using Visual Studio and not mingw. I have not tested to see how well mingw works with vendor libraries that are compiled with Visual Studio. I know for sure that Cygwin stopped working with vendor libraries that were compiled with Visual Studio quite a few years ago.
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of John Dobbins via Tech-talk
All,
I am attempting to install EPICS on Windows 10 per the EPICS "How-To"
https://docs.epics-controls.org/projects/how-tos/en/latest/getting-started/installation-windows.html
I encounter the errors shown below.
Note that I am not wedded to this method of installation. (I have installed on Windows before but so infrequently that each time is a new adventure.)
Any advice appreciated.
Thanks,
John Dobbins
Research Support Specialist Cornell High Energy Synchrotron Source Cornell University
../osi/os/WIN32/epicsTempFile.cpp: In function ‘FILE* epicsTempFile()’: ../osi/os/WIN32/epicsTempFile.cpp:33:20: error: ‘_tempnam’ was not declared in this scope; did you mean ‘tempnam’? 33 | char * pName = _tempnam ( "c:\\tmp", "epics" ); | ^~~~~~~~ | tempnam ../osi/os/WIN32/epicsTempFile.cpp:49:26: error: ‘_O_CREAT’ was not declared in this scope; did you mean ‘O_CREAT’? 49 | const int openFlag = _O_CREAT | _O_EXCL | _O_RDWR | | ^~~~~~~~ | O_CREAT ../osi/os/WIN32/epicsTempFile.cpp:49:37: error: ‘_O_EXCL’ was not declared in this scope; did you mean ‘O_EXCL’? 49 | const int openFlag = _O_CREAT | _O_EXCL | _O_RDWR | | ^~~~~~~ | O_EXCL ../osi/os/WIN32/epicsTempFile.cpp:49:47: error: ‘_O_RDWR’ was not declared in this scope; did you mean ‘O_RDWR’? 49 | const int openFlag = _O_CREAT | _O_EXCL | _O_RDWR | | ^~~~~~~ | O_RDWR ../osi/os/WIN32/epicsTempFile.cpp:50:9: error: ‘_O_SHORT_LIVED’ was not declared in this scope 50 | _O_SHORT_LIVED | _O_BINARY | _O_TEMPORARY; | ^~~~~~~~~~~~~~ ../osi/os/WIN32/epicsTempFile.cpp:50:26: error: ‘_O_BINARY’ was not declared in this scope; did you mean ‘O_BINARY’? 50 | _O_SHORT_LIVED | _O_BINARY | _O_TEMPORARY; | ^~~~~~~~~ | O_BINARY ../osi/os/WIN32/epicsTempFile.cpp:50:38: error: ‘_O_TEMPORARY’ was not declared in this scope 50 | _O_SHORT_LIVED | _O_BINARY | _O_TEMPORARY; | ^~~~~~~~~~~~ ../osi/os/WIN32/epicsTempFile.cpp:51:38: error: ‘_S_IWRITE’ was not declared in this scope; did you mean ‘S_IWRITE’? 51 | int fd = open ( pName, openFlag, _S_IWRITE ); | ^~~~~~~~~ | S_IWRITE ../osi/os/WIN32/epicsTempFile.cpp:54:20: error: ‘_fdopen’ was not declared in this scope; did you mean ‘fdopen’? 54 | pNewFile = _fdopen ( fd, "w+b" ); | ^~~~~~~ | fdopen ../osi/os/WIN32/epicsTempFile.cpp:59:43: error: ‘errno’ was not declared in this scope 59 | "\"%s\"\n", pName, strerror ( errno ) ); | ^~~~~ ../osi/os/WIN32/epicsTempFile.cpp:23:1: note: ‘errno’ is defined in header ‘<cerrno>’; did you forget to ‘#include <cerrno>’? 22 | #include "epicsTempFile.h" +++ |+#include <cerrno> 23 | Installing PERL_MODULES file ../../../../lib/perl/EPICS/macLib.pm make[4]: *** No rule to make target 'epicsTempFile.obj', needed by 'antelope.exe'. Stop. make[4]: Leaving directory '/home/admin-jad22/base-7.0.3.1/modules/libcom/src/O.windows-x64-mingw' make[3]: *** [../../../configure/RULES_ARCHS:58: install.windows-x64-mingw] Error 2 make[3]: Leaving directory '/home/admin-jad22/base-7.0.3.1/modules/libcom/src' make[2]: *** [../../configure/RULES_DIRS:84: src.install] Error 2 make[2]: Leaving directory '/home/admin-jad22/base-7.0.3.1/modules/libcom' make[1]: *** [../configure/RULES_DIRS:84: libcom.install] Error 2 make[1]: Leaving directory '/home/admin-jad22/base-7.0.3.1/modules' make: *** [configure/RULES_DIRS:84: modules.install] Error 2
This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI. |