Re: [Mingw-w64-public] 2.0.8 doesn't build gcc 4.8.0?

2013-09-05 Thread Adrien Nader
On Wed, Sep 04, 2013, Roger Pack wrote:
 Hello.
 Despite my not understanding it, for some reason with 2.0.8 I'm unable
 to build gcc 4.8.0, I get this output:
 
 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55706
 
 however, that should have been fixed in r4357, which should have
 been included in 2.0.8, so I'm at a bit of a loss.  Any ideas?
 (My first thought is...maybe once the VARIANT stuff stabilizes a new
 release would be possible?)  It'd be nice to get off svn.
 Thank you all.
 -roger-
Hi,

You need CRT from trunk.

Actually the mainpage states Version 3.0 In trunk, and nearing release,
has some Large File Support. Note that GCC-4.8.x requires at least r5437
from trunk to support C++11 std::to_string. Earlier versions will not
work. 

(ok, that's a very recent change)

5437 and not 4357; maybe there has been some mixup.

-- 
Adrien Nader

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] 2.0.8 doesn't build gcc 4.8.0?

2013-09-05 Thread Ray Donnelly
For most projects that use it, mingw-w64 is grabbed from svn and the
releases are largely ignored.

Whether that's a good thing or not is another matter of course.

On Thu, Sep 5, 2013 at 3:17 PM, Roger Pack rogerdpa...@gmail.com wrote:
 On 9/5/13, Adrien Nader adr...@notk.org wrote:
 On Wed, Sep 04, 2013, Roger Pack wrote:
 Hello.
 Despite my not understanding it, for some reason with 2.0.8 I'm unable
 to build gcc 4.8.0, I get this output:

 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55706

 however, that should have been fixed in r4357, which should have
 been included in 2.0.8, so I'm at a bit of a loss.  Any ideas?
 (My first thought is...maybe once the VARIANT stuff stabilizes a new
 release would be possible?)  It'd be nice to get off svn.
 Thank you all.
 -roger-
 Hi,

 You need CRT from trunk.

 Actually the mainpage states Version 3.0 In trunk, and nearing release,
 has some Large File Support. Note that GCC-4.8.x requires at least r5437
 from trunk to support C++11 std::to_string. Earlier versions will not
 work. 

 Ok looking forward to future releases then :)
 -roger-

 --
 Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
 Discover the easy way to master current and previous Microsoft technologies
 and advance your career. Get an incredible 1,500+ hours of step-by-step
 tutorial videos with LearnDevNow. Subscribe today and save!
 http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk
 ___
 Mingw-w64-public mailing list
 Mingw-w64-public@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] 2.0.8 doesn't build gcc 4.8.0?

2013-09-05 Thread niXman
2013/9/5 Ray Donnelly:
 For most projects that use it, mingw-w64 is grabbed from svn and the
 releases are largely ignored.

 Whether that's a good thing or not is another matter of course.

This situation will be corrected. We(I and Alexey) will building using
mingw-w64 releases, just the names of builds will have some another
notation.



-- 
Regards,
niXman
___
Dual-target(32  64-bit) MinGW compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingwbuilds/
___
Another online IDE: http://liveworkspace.org/

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


[Mingw-w64-public] #ifndef or #ifdef, that is the dilemma

2013-09-05 Thread Incongruous
#ifndef __cpluplus
   std::cout  error\n A C++ compiler is required!  std::endl;
   return -1;
#endif 
The above snip says, if __cplusplus has not been defined print  “bla bla” and 
return –1. Which means that if I am using __cplusplus it should NOT print 
anthing, right? So, am I using the C or the C++ compiler? I am really confused. 

TIA--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public