Front page | perl.perl5.porters |
Postings from January 2005
I don't really think it is necessary to change anything relating to echo. However, at the top of my wish list is looking for htonl in sys/socket.h as that is where you will find it on a Windows platform, but of course if you did that, it would only be a part of the solution and the little tests Configure compiles might not be compiling under Windows anyway. If you don't link to libmsvcrt.a you get an error finding WinMain@16. At least I think that is the solution. The second thing on the wishlist is not assuming a usable 'struct dirent' given dirent.h. MinGW has that and direct.h. Although I am not an authority, I think having both might inevitably confuse any configure script. The problem is MinGW is not written for msys, msys is written for MinGW which is primarily intended to be used in cmd, not bash. Anyway, these are just ideas to put out there to make you more aware of the details if at any time it seems feasible to make Configure Windows friendly. Right now there is not much of a push for it in the Linux community, but at some point it will become obvious there are advantages to helping to port the great software written for Linux to Windows. Although of course has been ported to windows and I did succeed in porting Perl-5.8.6. Some of the newest options are not included though. If it worked with Configure, the Windows compile would stay uptodate automatically. That is the advantage, but it is still a decent compile using the newest verion of Perl. No complaints. I think I might check out comp.lang.perl.misc for some of my further questions. Stephen ----- Original Message ----- From: "Andy Dougherty via RT" <perlbug-followup@perl.org> To: <stecmccarthy@hotpop.com> Sent: Friday, January 28, 2005 11:38 AM Subject: Re: [perl #33948] configure checking echo > On Thu, 27 Jan 2005, Stephen wrote: > >> It is probably not a high >> priority, but Configure could use a little update. For instance, it >> includes sys/file.h instead of fcntl.h when sys/file.h in only a dummy >> that call fcntl.h anyway: > > Well, it might be on your system, but it's certainly not everywhere. > > Your broader point is correct -- Configure in many little ways still shows > its BSDish origins. However, it generally works, so there's little > incentive to muck with things that work :-). > > -- > Andy Dougherty doughera@lafayette.edu > >