Re: [Mingw-w64-public] rubenvb 4.7.1-2-release build

On 8/17/2012 11:45 AM, Ruben Van Boxem wrote: > I don't think cmd.exe supports backticks '`'. I suspected that much so that is why I downloaded the msys package and tried building with that. > GTK uses configure scripts etc. to build if I'm not mistaken. When you > run from MSYS you should call MS

Re: [Mingw-w64-public] rubenvb 4.7.1-2-release build

On 8/7/12, Damon Register wrote: > On 8/17/2012 4:18 AM, Ruben Van Boxem wrote: >> You should call only the executables in mingw32/bin, never directly use >> the ones >> in mingw32/i686-w64-mingw32/bin. The simplest way to set up a build >> environment is >> to doubleclick on "mingw32env.cmd". > T

Re: [Mingw-w64-public] rubenvb 4.7.1-2-release build

2012/8/7 Damon Register > On 8/17/2012 4:18 AM, Ruben Van Boxem wrote: > > You should call only the executables in mingw32/bin, never directly use > the ones > > in mingw32/i686-w64-mingw32/bin. The simplest way to set up a build > environment is > > to doubleclick on "mingw32env.cmd". > Thanks f

Re: [Mingw-w64-public] rubenvb 4.7.1-2-release build

On 8/17/2012 4:18 AM, Ruben Van Boxem wrote: > You should call only the executables in mingw32/bin, never directly use the > ones > in mingw32/i686-w64-mingw32/bin. The simplest way to set up a build > environment is > to doubleclick on "mingw32env.cmd". Thanks for the tip. I just downloaded the

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

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

-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

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

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] rubenvb 4.7.1-2-release build

On Fri, Aug 17, 2012 at 4:18 AM, Ruben Van Boxem wrote: > (I'm not entirely sure what the "c++" executable is > or does) It is a symlink or copy of g++. The same is true for gcc and cc. -- Earnie -- https://sites.google.com/site/earnieboyd --

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

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

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] rubenvb 4.7.1-2-release build

Works well on Ubuntu 12.04. I just compiled Qt5 + QtCreator + Qbs's test demos successful. Thanks for your great work! 2012/8/17 Ruben Van Boxem > Hi everyone, > > I kind of borked parts of my previous 4.7 release. I apologize again, > because I should have caught the problems reported before I

Re: [Mingw-w64-public] Obtaining stacktraces within a Windows application

On 16/08/12 21:34, Alex Loukissas wrote: > Hi folks, > > It appears that with addr2line I got quite far. Unfortunately, I haven't > been able to try out the libbfd option, since it appears that this > library isn't included in the standard ubuntu mingw package. Good thing it's not there; see

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

-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] [patch] mingw-w64-crt/configure.ac: sysroot handling

2012/8/17 Corinna Vinschen > On Aug 17 12:40, Ruben Van Boxem wrote: > > 2012/8/17 Corinna Vinschen > > > On Aug 17 12:19, Ruben Van Boxem wrote: > > > > For my Arch Linux cross-compilers I don't use a sysroot: there's no > > > point. > > > > Just install to prefix=/usr and be done with it. > >

Re: [Mingw-w64-public] [patch] mingw-w64-crt/configure.ac: sysroot handling

On Aug 17 12:40, Ruben Van Boxem wrote: > 2012/8/17 Corinna Vinschen > > On Aug 17 12:19, Ruben Van Boxem wrote: > > > For my Arch Linux cross-compilers I don't use a sysroot: there's no > > point. > > > Just install to prefix=/usr and be done with it. > > > Every prefixed binary is placed nicely

Re: [Mingw-w64-public] [patch] mingw-w64-crt/configure.ac: sysroot handling

2012/8/17 Corinna Vinschen > On Aug 17 12:19, Ruben Van Boxem wrote: > > 2012/8/17 Corinna Vinschen > > > On Aug 16 08:16, NightStrike wrote: > > > > Even if I agreed with the with-sysroot default, these should be > > > > committed as two separate things. So, approved for the /include bug. > >

Re: [Mingw-w64-public] [patch] mingw-w64-crt/configure.ac: sysroot handling

On Aug 17 12:19, Ruben Van Boxem wrote: > 2012/8/17 Corinna Vinschen > > On Aug 16 08:16, NightStrike wrote: > > > Even if I agreed with the with-sysroot default, these should be > > > committed as two separate things. So, approved for the /include bug. > > > We should talk about the with-sysroot

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

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] [patch] mingw-w64-crt/configure.ac: sysroot handling

2012/8/17 Corinna Vinschen > On Aug 16 08:16, NightStrike wrote: > > On Tue, Aug 14, 2012 at 3:30 AM, Corinna Vinschen > wrote: > > >> Index: configure.ac > > >> === > > >> --- configure.ac (revision 5352) > > >> +++ configure.

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

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] [patch] mingw-w64-crt/configure.ac: sysroot handling

On Aug 16 08:16, NightStrike wrote: > On Tue, Aug 14, 2012 at 3:30 AM, Corinna Vinschen wrote: > >> Index: configure.ac > >> === > >> --- configure.ac (revision 5352) > >> +++ configure.ac (working copy) > >> @@ -16,12 +16,1

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

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/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

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

-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

-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

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-

Re: [Mingw-w64-public] rubenvb 4.7.1-2-release build

Op 17 aug. 2012 01:44 schreef "Herb Thompson" het volgende: > > On 2012-08-16 3:32 PM, Ruben Van Boxem wrote: > > Hi everyone, > > > > ... > > > > I am in the process of uploading 4.7.1-2-release packages. I tested the > > i686-win32 compiler, and it doesn't crash. > > > > ... > > > > On my Win

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

-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