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: building EPICSR3.14.8.1 on MacOSX 10.3/10.4 |
From: | Eric Norum <[email protected]> |
To: | Noboru Yamamoto <[email protected]>, Marty Kraimer <[email protected]>, Janet Anderson <[email protected]> |
Cc: | "'[email protected]'" <[email protected]> |
Date: | Mon, 26 Dec 2005 12:31:28 -0600 |
It appears that this mixup occurred when epicsStdlib.c was added. What about making the following change? Index: epicsStdlib.c =================================================================== RCS file: /net/phoebus/epicsmgr/cvsroot/epics/base/src/libCom/misc/epicsStdlib.c,v retrieving revision 1.1.2.1 diff -u -r1.1.2.1 epicsStdlib.c --- epicsStdlib.c 12 Dec 2005 19:54:46 -0000 1.1.2.1 +++ epicsStdlib.c 26 Dec 2005 18:22:40 -0000 @@ -43,6 +43,9 @@ return 1; } +#ifdef epicsStrtod +# undef epicsStrtod +#endif epicsShareFunc double epicsStrtod( const char *str, char **endp) { I'm quite surprised that this problem didn't show up during pre-release testing. I suspect that it will cause the same infinite recursion on all POSIX targets. On Dec 26, 2005, at 12:14 AM, Noboru Yamamoto wrote:
|