Mail Archives: djgpp-workers/2001/11/20/08:02:50
> From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
> Date: Tue, 20 Nov 2001 22:21:23 +1100
>
> I downloaded the CVS 2.5f code as this was suggested by the current Grep
> maintainer that this may fix the it. I now get past the HAVE_LIBPCRE and now
> find that DJGPP does not have support for S_ISSOCK(stats->stat.st_mode)
> which was introduced in the changes since 2.5e. Should I get arround this by
> defining it out for DJGPP as per the change below or define it in sys\stat.h
> to always be false such as:-
> #define S_ISSOCK(m) (0x00)
None of the above, IMHO. S_ISSOCK is not sufficiently portable (even
though the latest draft of Posix requires it) for programs to use it
freely. I think Grep should only use S_ISSOCK if it is defined, not
only for DJGPP.
> > I have a few questions about this:-
> > 1) Should I delete the redundant files in the DJGP directory?
> > 2) Should I move the djgpp\readme file to the main grep directory and
> > rename it to readme.dos?
> > 3) Is there any problem as "releasing" this as an alpha release for
> > DJGPP? By releaseing I mean put it on the main html page at clio and put
> the
> > sources and binary files to the incoming directory at delorie.com? (I need
> > to build a 2.03+ DJGPP setup on my Win 98 PC before I can produce the
> binary
> > files to send )
> > 4) Are important are the documentation zip files?
>
> Anyone disagree with the following suggestions:-
> 1) Yes
Agreed; but please make sure what you delete is indeed redundant ;-)
> 2) Yes
This is up to the package maintainer.
> 3) No
Maybe, I don't know. Are there any significant user-level changes in
this versions as compared to 2.4?
In any case, if you can test the build on a non-LFN platform, it's
highly recommended.
> 4) Unknown.
Not very important, but if you have the time to produce them and the
bandwidth to upload them, why not?
- Raw text -