On Monday 15 March 2010 09:13:24 Tatsuro MATSUOKA wrote:
> Today I have installed gcc-4.5.0-mingw.
I presume you mean gcc-4.5.0-mingw32, to differentiate from any
release by the w64 team.
> I have tried to use them to build the gnuplot.
You don't need to go to that length; a good bug report *doesn't*
cloud the issue by referring unnecessarily to any external project.
> In compling, the compliler claimed that ctype.h was not found.
This is a compiler bug. It can be readily confirmed by:
$ echo '#include <ctype.h>' | gcc -E -xc -
and the cause can be clearly seen, by adding gcc's -v flag:
$ echo '#include <ctype.h>' | gcc -v -E -xc -
(or likewise for any other system header file from mingwrt or from
w32api). However, the bug will not be apparent, if you've installed
in the recommended standard sysroot path, i.e. C:\MinGW; (or indeed,
if you have a prior installation with that sysroot).
> So I add -I/mingw/include to the CFLAG of the makefile of mingw
> version gnuplot. The complie process went well.
> Have to I add -I/mingw/include in compling?
You *shouldn't* have to, but until this bug is fixed that is one way
to work around it. Other possibilities, which may prove to be more
convenient, are to re-install into the standard C:\MinGW sysroot, or
to have gcc dump a specs file, and configure the extra include path
On Monday 15 March 2010 11:23:31 Earnie replied:
> Be sure to file a bug report for the SF MinGW project. We can't
> track the email.
Yes, bugs filed on the appropriate tracker are less likely to be
forgotten, and will likely be granted higher priority. If you'd
like to file a report, I'll add some further follow-up info to it,
tomorrow afternoon (GMT).