Is cygwin newlib reentrant?
Hi All, Does anyone know if the newlib that comes with cygwin is reentrant or not. I know that we can compile newlib to be reentrant by providing -DREENTRANT_SYSCALLS_PROVIDED to the CFLAGS_FOR_TARGET variable in the makefile before building newlib. Not sure if this was done by the cygwin people. Thanks in advance. Kind regards, Anurag -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Is cygwin newlib reentrant??
Hi All, Does anyone know if the newlib that comes with cygwin is reentrant or not. I know that we can compile newlib to be reentrant by providing -DREENTRANT_SYSCALLS_PROVIDED to the CFLAGS_FOR_TARGET variable in the makefile before building newlib. Not sure if this was done by the cygwin people. Just looking for a simple Yes or No. Thanks in advance. Kind regards, Anurag -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Is cygwin newlib reentrant??
Hi I haven't had any response to this question. Can someone please tell me who the maintainer of the cygwin/newlib package is? I will address the question straight to him/her. Thanks. Anurag On Fri, 11 Oct 2002 11:22:56 +1000 Anurag Sharma <[EMAIL PROTECTED]> wrote: > Hi All, > > Does anyone know if the newlib that comes with cygwin is reentrant or > not. I know that we can compile newlib to be reentrant by providing > -DREENTRANT_SYSCALLS_PROVIDED to the CFLAGS_FOR_TARGET variable in the > makefile before building newlib. Not sure if this was done by the cygwin > people. > > Just looking for a simple Yes or No. > > Thanks in advance. > > Kind regards, > > Anurag > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
errno reset when using thread enabled gcc
Hi All,
I have come across a strange behaviour using native gcc on cygwin. I
understand that this issue is not 100% relevant to this list, but I am
hoping some one might have come across this issue before. Apologies for
any incovinience. I have posted the same on newlib mailing list too.
Consider this short code:
int fd = ::open("/tmp/errnotest", O_RDONLY | O_BINARY);
if (fd == -1) {
std::cerr << "open failed, errno=" << errno << ", strerror=" <<
strerror(errno) << std::endl;
std::cerr << "open failed, errno=" << errno << ", strerror=" <<
strerror(errno) << std::endl;
}
If I build the gcc compiler by providing --enable-threads=single option
in the configure stage, following is the output :
open failed, errno=2, strerror=No such file or directory
open failed, errno=2, strerror=No such file or directory
This is of course expected.
Hoewever if I build the compiler by providing --enable-threads=posix
option in the configure stage, the output is as follows :
open failed, errno=2, strerror=No such file or directory
open failed, errno=0, strerror=No error
That is , after the first call to errno, it is reset!!
Has anyone else experiened this before? Can anyone please help find out
what exactly is going wrong?
Regards,
Anurag
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: errno reset when using thread enabled gcc
On Thu, 17 Oct 2002 10:09:26 -0400 (EDT)
Igor Pechtchanski <[EMAIL PROTECTED]> wrote:
> On Thu, 17 Oct 2002, Anurag Sharma wrote:
>
> > Hi All,
> >
> > I have come across a strange behaviour using native gcc on cygwin. I
> > understand that this issue is not 100% relevant to this list, but I am
> > hoping some one might have come across this issue before. Apologies
> > for any incovinience. I have posted the same on newlib mailing list
> > too.
> >
> > Consider this short code:
> >
> >int fd = ::open("/tmp/errnotest", O_RDONLY | O_BINARY);
> >
> > if (fd == -1) {
> > std::cerr << "open failed, errno=" << errno << ", strerror="
> > << strerror(errno) << std::endl; std::cerr << "open failed,
> > errno=" << errno << ", strerror=" << strerror(errno) <<
> > std::endl;
> > }
> >
> > If I build the gcc compiler by providing --enable-threads=single
> > option in the configure stage, following is the output :
> >
> > open failed, errno=2, strerror=No such file or directory
> > open failed, errno=2, strerror=No such file or directory
> >
> > This is of course expected.
> >
> > Hoewever if I build the compiler by providing --enable-threads=posix
> > option in the configure stage, the output is as follows :
> >
> > open failed, errno=2, strerror=No such file or directory
> > open failed, errno=0, strerror=No error
> >
> > That is , after the first call to errno, it is reset!!
> >
> > Has anyone else experiened this before? Can anyone please help find
> > out what exactly is going wrong?
> >
> > Regards,
> >
> > Anurag
>
> Anurag,
>
> While I don't know for sure that this is what's happening, have you
> considered that operator<< or endl may (re)set errno?
> Igor
Yes Igor,
It is the STL iostream operators which are resetting it. Using the
threading model of posix does make the STL thread safe, but why should it
affect errno?
Thanks for your response.
Reagrds,
Anurag
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: gcc-3.2-3: bootstrap build fails (HAVE_DECL_GETOPT not in config.h?)
Hi All, Has there been a resolution to this issue? I can't see any answeres in the previous posts. Regards, Anurag On Wed, 20 Nov 2002 10:14:59 +1100 Nigel Stewart & Fiona Smith <[EMAIL PROTECTED]> wrote: > Michael, > > I have encountered the same problem on my setup. > > Regards, > > Nigel Stewart > > >Trying to build gcc-3.2-3 from scratch. Have the near latest versions > >of everything in cygwin (see cygcheck.out). > > > >/home/mhcox/projects/build/gcc-3.2-3/gcc/xgcc -shared-libgcc > >-B/home/mhcox/p rojects/build/gcc-3.2-3/gcc/ -nostdinc++ > >-L/home/mhcox/projects/build/gcc-3. 2-3/i686-pc-cygwin/libstdc++-v3/src > >-L/home/mhcox/projects/build/gcc-3.2-3/i > >686-pc-cygwin/libstdc++-v3/src/.libs > >-B/home/mhcox/projects/install/i686-pc- cygwin/bin/ > >-B/home/mhcox/projects/install/i686-pc-cygwin/lib/ > >-isystem/home/mhcox/projects/install/i686-pc-cygwin/include > >-I/usr/src/gcc-3.2-3/lib stdc++-v3/../gcc > >-I/usr/src/gcc-3.2-3/libstdc++-v3/../include -I/home/mhcox/ > >projects/build/gcc-3.2-3/i686-pc-cygwin/libstdc++-v3/include/i686-pc-c > >ygwin > >-I/home/mhcox/projects/build/gcc-3.2-3/i686-pc-cygwin/libstdc++-v3/inc > >lude - I/usr/src/gcc-3.2-3/libstdc++-v3/libsupc++ -g -O2 > >-fno-implicit-templates -W all -Wno-format -W -Wwrite-strings -Winline > >-fdiagnostics-show-location=once > > -ffunction-sections -fdata-sections -g -c > >/usr/src/gcc-3.2-3/libstdc++-v3/libsupc++/pure.cc -o pure.o > >cc1plus: warning: -ffunction-sections may affect debugging on some > >targets In file included from /usr/include/unistd.h:8, > > from > > /usr/src/gcc-3.2-3/libstdc++-v3/libsupc++/pure.cc:34: > >/usr/src/gcc-3.2-3/include/getopt.h:115: declaration of C function `int > > getopt()' conflicts with > >/usr/include/sys/unistd.h:125: previous declaration `int getopt(int, > >char* > > const*, const char*)' here > > > > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: gcc-3.2-3: bootstrap build fails (HAVE_DECL_GETOPT not in config.h?)
Christopher, If it works for you. Great! The idea of my post was to ask the advice of those people who were having this problem. Resolution is necessary for those of us who are having this problem. I didn't request you in particular to help me, so if you can't offer any helpfull hints don't bother. I will move on. Regards, Anurag On Tue, 3 Dec 2002 11:35:17 -0500 Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Tue, Dec 03, 2002 at 05:25:06PM +1100, Anurag Sharma wrote: > >Hi All, > > > >Has there been a resolution to this issue? I can't see any answeres in > >the previous posts. > > No resolution is necessary. It works fine for me. I'm the package > maintainer. > > If it doesn't work for you then make some obvious changes to the header > files and move on. > > cgf > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
set - unset not working
Hi Team, i have installed the latest version of the CYgwin ( 1.7 ) , for the build activities of the NT builds. i am not able to set/unset env variables. every time the following error pops up : set/unset not recognized as internal or external command. i have latest bash installed. i am not able to find the set/unset exe in the cygwin\bin folder. please help. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
