No. You gave an answer to a question Incongruous did not ask.
Unfortunately, your answer could confuse newcomers searching this ML.
Read Incongruous' post again. It said "I would like to test for MinGW64 to
include or exclude some code..."
I think LRN, Ruben, and the FAQ provided the correct answ
If you use gnu autotools it's really simple. Just put something like this
into configure.ac
AC_CHECK_HEADERS(windows.h)
And then use
#ifdef HAVE_WINDOWS_H
do this
#else
do that
#endif
2013/10/16 Incongruous
> Thanks everyone.
>
> *From:* Incongruous
> *Sent:* Tuesday, October 15, 2013 6
You are absolutely right. I took a look into fcntl.h and there it was.
Apparently my configure script is defining NO_OLDNAMES and not defining
_POSIX. I dunno why. But the _O_BINARY option works just fine and allows
me to avoid the hack with fopen/fileno.
Thanks a bunch. Now I can go ahead and r
On 10/16/13, Edscott Wilson wrote:
> 2013/10/16 Ruben Van Boxem
>
>> 2013/10/16 Edscott Wilson
>>
>>>
>>> I appreciate all the responses. This is the result.
>>>
>>> 1. The option O_BINARY is not available in fcntl.h for gcc, So
>>> open("test.dbh", O_RDWR|O_BINARY) does not work.
>>>
>>
>> See
2013/10/16 Ruben Van Boxem
> 2013/10/16 Edscott Wilson
>
>>
>> I appreciate all the responses. This is the result.
>>
>> 1. The option O_BINARY is not available in fcntl.h for gcc, So
>> open("test.dbh", O_RDWR|O_BINARY) does not work.
>>
>
> See MSDN for the flags you are looking for:
> http://
Problem with fseek is:
int fseek(FILE *stream, long offset, int whence);
While lseek:
off_t lseek(int fd, off_t offset, int whence);
On 32 bit systems, fseek is limited to 2 GB. Usage of lseek allows for use
of off_t, which with mingw-64, will be 64 bit and allow for files > 2 GB.
2013/10/1
Edscott Wilson писал 2013-10-16 18:53:
> ... Since I require use of lseek() ...
man fseek
--
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/
___
Thanks everyone.
From: Incongruous
Sent: Tuesday, October 15, 2013 6:06 AM
To: MinGW-64 Mailinglist
Subject: [Mingw-w64-public] to test for MinGW64
I would like to test for MinGW64 to include or exclude some code; something
like:
#ifdef MinGW64
doThis();
#endif
#ifdef __MSV__
doSomthingElse
#e
2013/10/16 Edscott Wilson
>
> I appreciate all the responses. This is the result.
>
> 1. The option O_BINARY is not available in fcntl.h for gcc, So
> open("test.dbh", O_RDWR|O_BINARY) does not work.
>
See MSDN for the flags you are looking for:
http://msdn.microsoft.com/en-us/library/z0kc8e3z.a
I appreciate all the responses. This is the result.
1. The option O_BINARY is not available in fcntl.h for gcc, So
open("test.dbh", O_RDWR|O_BINARY) does not work.
2. Neither will the unix2dos program work since the file to open is a
binary file which must be read byte by byte.
3. fopen("test.db
Hello LRN,
both patches are ok for trunk. Please apply.
Thanks,
Kai
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15.10.2013 17:00, Kai Tietz wrote:
> Well, I don't believe in Voodoo here. My bets would go for builtin
> function vs. C-library function. Is there actually such a function in
> msvcrt?
No, there is no stpcpy in msvcrt.
On 15.10.2013 16:55, Ruben
-Original Message-
From: JonY
Sent: Monday, October 07, 2013 12:00 AM
To: mingw-w64-public@lists.sourceforge.net
Subject: Re: [Mingw-w64-public] quadmath.h's expq() crashes at runtime.
> On 10/6/2013 20:31, sisyph...@optusnet.com.au wrote:
> > Hi,
> >
> > Here's the simple demo:
> >
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15.10.2013 19:14, LRN wrote:
> On 15.10.2013 16:34, LRN wrote:
>> Testcase is attached. Some invocations of stpcpy work, some don't.
>
> expand_builtin_stpcpy() from gcc/builtins.c sheds some light on this
> (when return value is ignored, stpcpy()
14 matches
Mail list logo
