Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Ruben Van Boxem
2012/8/17 Ozkan Sezer > On 8/17/12, Earnie Boyd wrote: > > On Fri, Aug 17, 2012 at 9:37 AM, Ozkan Sezer wrote: > >>> information, see Windows Runtime Unsupported CRT Functions." How does > >>> one know when they are "in the Windows Runtime"? I.E. How can we > >>> guard against an application

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 17.08.2012 14:12, schrieb Rainer Emrich: > Am 17.08.2012 12:17, schrieb Ozkan Sezer: >> gcc/system.h has its declaration guarded by #if defined >> (HAVE_DECL_GETCWD) && !HAVE_DECL_GETCWD ... so the question is why >> doesn't it work and the header h

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Ozkan Sezer
On 8/17/12, Earnie Boyd wrote: > On Fri, Aug 17, 2012 at 9:37 AM, Ozkan Sezer wrote: >>> information, see Windows Runtime Unsupported CRT Functions." How does >>> one know when they are "in the Windows Runtime"? I.E. How can we >>> guard against an application using the CRT functions that are n

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Earnie Boyd
On Fri, Aug 17, 2012 at 9:37 AM, Ozkan Sezer wrote: >> information, see Windows Runtime Unsupported CRT Functions." How does >> one know when they are "in the Windows Runtime"? I.E. How can we >> guard against an application using the CRT functions that are not >> supported "in the Windows Runti

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Ozkan Sezer
On 8/17/12, Earnie Boyd wrote: > On Fri, Aug 17, 2012 at 6:12 AM, Jacek Caban wrote: >> >> That's a good question, it seems like MSVC has only one declaration in >> direct.h. I don't know why do we have it duplicated in io.h. IMO we >> should consider removing it from there, leaving only direct.h

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Earnie Boyd
On Fri, Aug 17, 2012 at 6:12 AM, Jacek Caban wrote: > > That's a good question, it seems like MSVC has only one declaration in > direct.h. I don't know why do we have it duplicated in io.h. IMO we > should consider removing it from there, leaving only direct.h version. My guess is that the MS dire

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 17.08.2012 12:17, schrieb Ozkan Sezer: > gcc/system.h has its declaration guarded by #if defined (HAVE_DECL_GETCWD) > && !HAVE_DECL_GETCWD ... so the question is why doesn't it work and the > header has to declare a library function by itself? > in

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Ruben Van Boxem
2012/8/17 Ozkan Sezer > On 8/17/12, Ruben Van Boxem wrote: > > 2012/8/17 Jacek Caban > > > >> On 08/17/12 11:42, Rainer Emrich wrote: > >> > Am 17.08.2012 11:29, schrieb Kai Tietz: > >> > > Hallo Rainer, > >> > > >> > > well, the issue is that msvcrt's getcwd has as second argument the > >> > >

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Ozkan Sezer
On 8/17/12, Ruben Van Boxem wrote: > 2012/8/17 Jacek Caban > >> On 08/17/12 11:42, Rainer Emrich wrote: >> > Am 17.08.2012 11:29, schrieb Kai Tietz: >> > > Hallo Rainer, >> > >> > > well, the issue is that msvcrt's getcwd has as second argument the >> > > pointer-length-argument typed as 'int'.

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Jacek Caban
On 08/17/12 11:33, Rainer Emrich wrote: > Am 17.08.2012 09:37, schrieb Rainer Emrich: > > After the gcc cxx-conversion merge has taken place, I get a conflicting > > declaration of getcwd in io.h in several places while bootstrapping > > gcc-4.8.0. > > > In file included from ../../../src/gcc-4.8.0

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Ruben Van Boxem
2012/8/17 Jacek Caban > On 08/17/12 11:42, Rainer Emrich wrote: > > Am 17.08.2012 11:29, schrieb Kai Tietz: > > > Hallo Rainer, > > > > > well, the issue is that msvcrt's getcwd has as second argument the > > > pointer-length-argument typed as 'int'. You can check this also by > > > seaching on

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Jacek Caban
On 08/17/12 11:42, Rainer Emrich wrote: > Am 17.08.2012 11:29, schrieb Kai Tietz: > > Hallo Rainer, > > > well, the issue is that msvcrt's getcwd has as second argument the > > pointer-length-argument typed as 'int'. You can check this also by > > seaching on msdn for getcwd. For 32-bit it is just

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 17.08.2012 11:29, schrieb Kai Tietz: > Hallo Rainer, > > well, the issue is that msvcrt's getcwd has as second argument the > pointer-length-argument typed as 'int'. You can check this also by > seaching on msdn for getcwd. For 32-bit it is just

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 17.08.2012 09:37, schrieb Rainer Emrich: > After the gcc cxx-conversion merge has taken place, I get a conflicting > declaration of getcwd in io.h in several places while bootstrapping > gcc-4.8.0. > > In file included from ../../../src/gcc-4.8.0/

Re: [Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Kai Tietz
Hallo Rainer, well, the issue is that msvcrt's getcwd has as second argument the pointer-length-argument typed as 'int'. You can check this also by seaching on msdn for getcwd. For 32-bit it is just a sign-difference of this argument, which is pretty unlikely to reach (0x7fffu + 1u). For 64-

[Mingw-w64-public] Conflicting declaration of getcwd in io.h

2012-08-17 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After the gcc cxx-conversion merge has taken place, I get a conflicting declaration of getcwd in io.h in several places while bootstrapping gcc-4.8.0. In file included from ../../../src/gcc-4.8.0/gcc/ggc-common.c:25:0: ../../../src/gcc-4.8.0/gcc/syste