Re: [Mingw-w64-public] New automated build for mingw?

2012-03-23 Thread NightStrike
To be clear, I meant Jon_Y. Buildbot already does everything we need, and it takes one click to fire off an "official release". The daily building is vital. It's a huge key to our success. What we need, and how people can help, is access to more windows slaves. All the ones we have left are mi

Re: [Mingw-w64-public] New automated build for mingw?

2012-03-23 Thread NightStrike
The below is an email that I 100% fully support. Thank you, Jon. On Thu, Mar 22, 2012 at 12:15 PM, JonY wrote: > On 3/23/2012 05:01, Jon wrote: >>> Would it be possible to generate a new automated build for mingw?  If >>> I remember correctly the mingw build-bots were down? >> >> Perhaps it's ti

Re: [Mingw-w64-public] New automated build for mingw?

2012-03-23 Thread JonY
On 3/24/2012 06:09, Jon wrote: >>> I'm not against CI, but I think something more lightweight, something more >>> attractive enough to potential new maintainers, and something easily >>> replicated/setup for only official project release builds is the solution. >>> And buildbot doesn't go away,

Re: [Mingw-w64-public] New automated build for mingw?

2012-03-23 Thread Jon
> > I'm not against CI, but I think something more lightweight, something more > > attractive enough to potential new maintainers, and something easily > > replicated/setup for only official project release builds is the solution. > > And buildbot doesn't go away, it just gets used internally by

Re: [Mingw-w64-public] New automated build for mingw?

2012-03-23 Thread Jon
> Would it be possible to generate a new automated build for mingw? If > I remember correctly the mingw build-bots were down? In this important discussion, has the original request been drowned out? Chris, please excuse my threadjacking poor form. Jon --

Re: [Mingw-w64-public] New automated build for mingw?

2012-03-23 Thread JonY
On 3/23/2012 09:23, Jon wrote: >>> How often are automated builds really needed? Once a week? Once a month? >>> Once a quarter? >>> >> >> Done everyday. > > Sorry, I overloaded "automated builds"...should be "How often are regular > project release builds really needed?" I think most users would

[Mingw-w64-public] Problems with cross-compile from linux to win32: linking process add __impl__ prefix to function names

2012-03-23 Thread Leandro Santiago
Hello to all. I'm using ubuntu 11.04 (32-bits) to cross-compile some static libraries to windows. I'm using mingw-w32 1.0, downloded from mingw-64 sf page. In some libraries I'm compiling, I have an error in the link time, when in the line of the source when e.g a function called myFunction() is

Re: [Mingw-w64-public] Problems with cross-compile from linux to win32: linking process add __impl__ prefix to function names

2012-03-23 Thread Leandro Santiago
2012/3/22 Leandro Santiago : > Hello to all. I'm using ubuntu 11.04 (32-bits) to cross-compile some > static libraries to windows. > > I'm using mingw-w32 1.0, downloded from mingw-64 sf page. > > In some libraries I'm compiling, I have an error in the link time, > when in the line of the source wh

Re: [Mingw-w64-public] Fwd: host/build/target for multilib cross compiler

2012-03-23 Thread niXman
2012/3/23 Kai Tietz : > niXman:  Eg you have the gcc-repository checked out in C:/sources/gcc. >  And you are using the prefix = C:/myprefix.  Then you need to setup > in C:/sources a symbolic link named "winsup" pointing to C:/myprefix. > Don't miss that you have in C:/myprefix a symbolic link - n

Re: [Mingw-w64-public] new GCC 4.7 rubenvb Personal build

2012-03-23 Thread Joshua Boyce
On Fri, Mar 23, 2012 at 1:54 PM, Joshua Boyce wrote: > On Mon, Mar 12, 2012 at 12:46 AM, Ruben Van Boxem < > vanboxem.ru...@gmail.com> wrote: > >> Hi all, >> >> I'm in the process of uploading a new build of GCC 4.7, with the >> llibstdc++ dll fix for std::thread. No more "-static" necessary anym

Re: [Mingw-w64-public] Crash gcc/g++ version 4.7.0

2012-03-23 Thread Ruben Van Boxem
Op 23 mrt. 2012 01:27 schreef "niXman" het volgende: > > 2012/3/23 niXman : > > 2012/3/23 Kai Tietz : > >> As they were built, it is pretty unlikely that the compiler itself has > >> an issue. It must be related to your environment. Maybe PATH not > >> proper set to DLL, or calling wrong tools,