On Wed, 2009-05-06 at 12:01 -0400, guile-user-requ...@gnu.org wrote:
> Ludovic Courts wrote:
> > Richard Shann writes:
> >
> >> conftest.c:94:19: regex.h: No such file or directory
> >
> > That means that either is simply not available in MinGW,
> or
> > it's optional, I don't know.
> >
>
> Yo
Ludovic Courtès wrote:
> Richard Shann writes:
>
>> conftest.c:94:19: regex.h: No such file or directory
>
> That means that either is simply not available in MinGW, or
> it's optional, I don't know.
>
You can find a suitable regex implementation at the MinGW project
download page:
http://sou
Thanks very much for the help, I'll have to look further at mingw.
Richard
>
> > conftest.c:94:19: regex.h: No such file or directory
>
> That means that either is simply not available in MinGW, or
> it's optional, I don't know.
>
> Thanks,
> Ludo'.
>
Hello,
Richard Shann writes:
> conftest.c:94:19: regex.h: No such file or directory
That means that either is simply not available in MinGW, or
it's optional, I don't know.
Thanks,
Ludo'.
> It should be available as long as Guile is configured with
> `--enable-regex' (which is the default) and regcomp(3) is provided by
> the C library, which I'd expect to be the case here.
>
> Can you show the result of "grep regcomp config.log" when configured
> on
> MinGW?
This gives nothing bu
Richard Shann writes:
> In porting GNU Denemo to windows I noticed that make-regexp is not
> present.
It should be available as long as Guile is configured with
`--enable-regex' (which is the default) and regcomp(3) is provided by
the C library, which I'd expect to be the case here.
Can you sho
2009/5/2 Richard Shann :
> In porting GNU Denemo to windows I noticed that make-regexp is not
> present. I found an obscure comment in one file that indicates this is a
> known limitation. Can anyone confirm this? Are there some release notes
> that I should have seen?
> Is it a problem that is lik
In porting GNU Denemo to windows I noticed that make-regexp is not
present. I found an obscure comment in one file that indicates this is a
known limitation. Can anyone confirm this? Are there some release notes
that I should have seen?
Is it a problem that is likely to be fixed?
Richard Shann
