This is the mail archive of the
mailing list for the Cygwin project.
Re: checking for working mmap...no
Am Donnerstag, 16. September 2004 um 10:47 schriebst du:
> On Sep 15 18:33, Sam Steingold wrote:
>> > * Christopher Faylor
>> <email@example.com> [2004-09-15 17:07:51
>> > On Wed, Sep 15, 2004 at 03:20:50PM -0400, Sam Steingold wrote:
>> >>It appears that cygwin mmap() is lacking:
>> >>configure:20536: checking for working mmap
>> >>configure:20617: gcc -o conftest.exe -g -O2 conftest.c >&5
>> >>configure:20620: $? = 0
>> >>configure:20622: ./conftest.exe
>> >>configure:20625: $? = 1
>> >>configure: program exited with status 1
>> >>configure: failed program was:
>> > It would be enormously helpful if you apprised us of exactly *what*
>> > was wrong rather than expecting us to figure it out.
>> Let me assure you that you know these matters much better than I do.
>> The C program in my original e-mail is supposed to terminate with exit
>> code 0 if mmap() works correctly. It does, e.g., on Linux and Solaris.
>> On cygwin, it terminates with exit code 1, which indicates that mmap()
>> does not work correctly as it is supposed to according to the spec.
>> Unfortunately, I am far from being an expert on these matters...
> The mmap test is crap. How can an application expect to be able to
> access just about every address together with MAP_FIXED?
> Consequentially MapViewOfFileEx returns error 487 in these cases,
> "Attempt to access invalid address."
> That's just another example of a crappy autoconf mmap test.
This means that mmap is actually working? Probably the best option
would be to fix the test in the upstream sources, so it will just work
automatically then? Maybe fixing it in the -devel autoconf release
for now would be sufficient too? Charles?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html