Re: [Mingw-w64-public] Why decimal floating point not supported for this target ?

2010-07-15 Thread Dongsheng Song
On Fri, Jul 16, 2010 at 13:17, Kai Tietz wrote: > The feature of decimal-floating-point isn't enabled in gcc for > cygwin/mingw targets. Question for those targets are, which > decimal-floating-point variant should be used, is there any support by > runtime, which ISO-Spec it the Decimal128 type

Re: [Mingw-w64-public] Why decimal floating point not supported for this target ?

2010-07-15 Thread Kai Tietz
Hello, 2010/7/16 Dongsheng Song : > Hi, > > When I compile the following simple C program: > > int main() > { >   _Decimal32 d1; >   _Decimal64 d2; >   _Decimal128 d3; > >   return 0; > } > > gcc 4.4 linux target is OK, but mingw32 or mingw64 target failed: > > C:\var\tmp\mingw32\bin>gcc testDecim

[Mingw-w64-public] Why decimal floating point not supported for this target ?

2010-07-15 Thread Dongsheng Song
Hi, When I compile the following simple C program: int main() { _Decimal32 d1; _Decimal64 d2; _Decimal128 d3; return 0; } gcc 4.4 linux target is OK, but mingw32 or mingw64 target failed: C:\var\tmp\mingw32\bin>gcc testDecimal.c testDecimal.c: In function 'main': testDecimal.c:3: error

[Mingw-w64-public] What library has strcpy_s and friends?

2010-07-15 Thread Greg Peele
I've been taking MinGW-w64 TDM-GCC 4.5 for a spin on my company's code and I ran into a problem compiling a third party dependency: CppUnit 1.12. Looks like MinGW defines __STDC_SECURE_LIB__ which causes CppUnit to use sprintf_s instead of sprintf (and similar functions). However, prototypes

Re: [Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread Prof Brian Ripley
Meanwhile (because I am working with 1.0) I have done a local svn merge and tested my example problems, which now compile. Thanks to all, especially Kai. On Thu, 15 Jul 2010, Ozkan Sezer wrote: On Thu, Jul 15, 2010 at 4:09 PM, Kai Tietz wrote: 2010/7/15 Ozkan Sezer : On Thu, Jul 15, 2010 a

Re: [Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread Kai Tietz
2010/7/15 Prof Brian Ripley : > Meanwhile (because I am working with 1.0) I have done a local svn merge and > tested my example problems, which now compile. > > Thanks to all, especially Kai. > > On Thu, 15 Jul 2010, Ozkan Sezer wrote: > >> On Thu, Jul 15, 2010 at 4:09 PM, Kai Tietz >> wrote: >>>

Re: [Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread Ozkan Sezer
On Thu, Jul 15, 2010 at 4:09 PM, Kai Tietz wrote: > 2010/7/15 Ozkan Sezer : >> On Thu, Jul 15, 2010 at 3:11 PM, t66...@gmail.com wrote: >>> Hi, >>> On 15/07/2010 9:50 PM, Kai Tietz wrote: 2010/7/15 Kai Tietz: > 2010/7/15 t66...@gmail.com: >> Hi >> On 15/07/2010 8:47 PM, Prof Bria

Re: [Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread Kai Tietz
2010/7/15 Ozkan Sezer : > On Thu, Jul 15, 2010 at 3:11 PM, t66...@gmail.com wrote: >> Hi, >> On 15/07/2010 9:50 PM, Kai Tietz wrote: >>> 2010/7/15 Kai Tietz: 2010/7/15 t66...@gmail.com: > Hi > On 15/07/2010 8:47 PM, Prof Brian Ripley wrote: >> We're working towards switching over

Re: [Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread Ozkan Sezer
On Thu, Jul 15, 2010 at 3:11 PM, t66...@gmail.com wrote: > Hi, > On 15/07/2010 9:50 PM, Kai Tietz wrote: >> 2010/7/15 Kai Tietz: >>> 2010/7/15 t66...@gmail.com: Hi On 15/07/2010 8:47 PM, Prof Brian Ripley wrote: > We're working towards switching over to post-April snapshots, but we >

Re: [Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread Ruben Van Boxem
> > Thanks for the hot patch at revision 2837 > I tried the patched headers and tried to compile the affected software > library again! This time it compiles successfully! > Great! Now no more need to work around it. > Let it be known throughout the world! Kai is tha bomb! ;) -

Re: [Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread t66...@gmail.com
Hi, On 15/07/2010 9:50 PM, Kai Tietz wrote: > 2010/7/15 Kai Tietz: >> 2010/7/15 t66...@gmail.com: >>> Hi >>> On 15/07/2010 8:47 PM, Prof Brian Ripley wrote: We're working towards switching over to post-April snapshots, but we have 1000s of R packages to recompile. A couple of those (so f

Re: [Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread Kai Tietz
2010/7/15 Kai Tietz : > 2010/7/15 t66...@gmail.com : >> Hi >> On 15/07/2010 8:47 PM, Prof Brian Ripley wrote: >>> We're working towards switching over to post-April snapshots, but we >>> have 1000s of R packages to recompile.  A couple of those (so far) >>> have thrown up header conflicts. >>> >>>

Re: [Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread Kai Tietz
2010/7/15 t66...@gmail.com : > Hi > On 15/07/2010 8:47 PM, Prof Brian Ripley wrote: >> We're working towards switching over to post-April snapshots, but we >> have 1000s of R packages to recompile.  A couple of those (so far) >> have thrown up header conflicts. >> >> Specifically for this report I

Re: [Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread t66...@gmail.com
Hi On 15/07/2010 8:47 PM, Prof Brian Ripley wrote: > We're working towards switching over to post-April snapshots, but we > have 1000s of R packages to recompile. A couple of those (so far) > have thrown up header conflicts. > > Specifically for this report I used > mingw-w64-1.0-bin_i686-mingw_20

[Mingw-w64-public] Header conflicts between and in recent builds of '1.0'

2010-07-15 Thread Prof Brian Ripley
We're working towards switching over to post-April snapshots, but we have 1000s of R packages to recompile. A couple of those (so far) have thrown up header conflicts. Specifically for this report I used mingw-w64-1.0-bin_i686-mingw_20100702.zip but I first found the problem with a Linux cros