Well I don't really feel like revisiting that argument... because there's
folks not on this list (and folks on it!) who really dislike us
duplicating all of libc.
Maybe a symlink is the best option for regex.h -- but I'd like to hear
from Rasmus what works best for php. If we do symlink, then there should
be a "rm -f regex.h" in the non-symlinked case so that you can
"./Configure" an existing source tree for another architecture safely.
Dean
On Sun, 1 Feb 1998, Rodent of Unusual Size wrote:
> Dean Gaudet wrote:
> >
> > Unfortunately there's one more catch... we can't put regex.h in
> > src/include. It breaks anywhere that doesn't use spencer regex.
>
> This spectre has been raised before: should we discard the option
> of OS regex versus src/regex? As I recall, there was a lot of "yes,
> let's always use ours" sentiment. The discussion got diluted into a
> general NIH one, and petered out somewhere in the ap_snprintf()
> area.
>
> Always using src/regex simplifies the build, puts this regex.h
> issue to bed, and incidentally raises our comfort level (well,
> potentially).
>
> #ken P-)}
>
|