Skip Menu |

This queue is for tickets about the Errno CPAN distribution.

Report information
The Basics
Id: 26155
Status: open
Priority: 0/
Queue: Errno

People
Owner: Nobody in particular
Requestors: sisyphus1 [...] optusnet.com.au
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Problems with Errno 1.10 and MinGW (Win32)
Date: Sun, 8 Apr 2007 09:44:14 +1000
To: <bug-Errno [...] rt.cpan.org>
From: "Sisyphus" <sisyphus1 [...] optusnet.com.au>
Hi, When building Errno-1.10 on a MinGW-built perl 5.8.8, 'dmake' produces the following output: ------------------------------- C:\perl58_M\bin\perl.exe Errno_pm.PL Errno.pm In file included from includes.c:17: C:/_32/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/stdarg.h:6:24: no include path in which to search for stdarg.h In file included from includes.c:56: C:/_32/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/stddef.h:6:24: no include path in which to search for stddef.h cp Errno.pm blib\lib/Errno.pm ------------------------------- (The version of gcc is 3.4.5.) Both stddef.h and stdarg.h are in the same location as the other header files listed in 'includes.c', so I guess the problem lies with the contents of those 2 problem headers. Here's what stdarg.h looks like (in its entirety): ------------------------------- /* * This is just an RC_INVOKED guard for the real stdarg.h * fixincluded in gcc system dir. One day we will delete this file. */ #ifndef RC_INVOKED #include_next<stdarg.h> #endif ------------------------------- stddef.h is essentially the same (the occurrrences of "stdarg" having been replaced with "stddef"). When 'dmake' test is run, failures are reported for tests 77, 205, 634, 887, 953, 1000, 1143, 1196, 1338, 1382, 1543, 1640, 1649 and 1738. I don't understand those 2 problem headers at all, and I couldn't work out what t\errno.t was doing - so I don't have any patches. But I'm certainly prepared to act upon any guidance I'm given on how to identify and resolve the issues. Cheers, Rob
Subject: Re: [rt.cpan.org #26155] Problems with Errno 1.10 and MinGW (Win32)
Date: Sat, 7 Apr 2007 20:08:40 -0500
To: bug-Errno [...] rt.cpan.org
From: Graham Barr <gbarr [...] pobox.com>
I am not familiar with MinGW, so any help I can give is limited. What if you modify Errno_pm.PL and add print INCS "#define RC_INVOKED 1\n"; around line 26. I suspect that you will not find the constants needed. However, I must ask why you feel the need to rebuild Errno. It is included with you perl installation Graham.
Subject: Re: [rt.cpan.org #26155] Problems with Errno 1.10 and MinGW (Win32)
Date: Mon, 9 Apr 2007 01:14:33 +1000
To: <bug-Errno [...] rt.cpan.org>
From: "Sisyphus" <sisyphus1 [...] optusnet.com.au>
Show quoted text
----- Original Message ----- From: "Graham Barr via RT" <bug-Errno@rt.cpan.org> To: <sisyphus1@optusnet.com.au> Sent: Sunday, April 08, 2007 11:36 AM Subject: Re: [rt.cpan.org #26155] Problems with Errno 1.10 and MinGW (Win32) .
> What if you modify Errno_pm.PL and add > > print INCS "#define RC_INVOKED 1\n"; > > around line 26.
Yes, you're suggested amendment gets rid of the warnings. Tests 77, 205, 632, 885, 951, 998, 1140, 1193, 1335, 1379, 1539, 1636, 1645 and 1734 still fail.
> > However, I must ask why you feel the need to rebuild Errno. It is > included with you perl installation >
I have no need to rebuild Errno. But having discovered that it doesn't build successfully with MinGW, I became a little concerned that this version of Errno might find its way into a future release of Perl. If that's not going to happen, then I've nothing to worry about, and I'm quite happy for you to "close" this bug without taking any further action. Cheers, Rob