Il 07/02/2011 19.48, Charles Wilson ha scritto:
On 2/7/2011 1:41 PM, Angelo Graziosi wrote:
Current trunk, rev. 169888, fails to bootstrap on Cygwin with this error:
[...]
/tmp/gcc-4.6-r169888/libgcc/config/libbid/bid_decimal_globals.c:47:18:
fatal error: fenv.h: No such file or directory
compilation terminated.
make[2]: *** [bid_decimal_globals.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
`/tmp/gcc-4.6-r169888/Work/i686-pc-cygwin/libgcc'
make[1]: *** [all-target-libgcc] Error 2
make[1]: Leaving directory `/tmp/gcc-4.6-r169888/Work'
make: *** [all] Error 2
This was a deliberate choice: e.g. to require a development version of
cygwin in order to bootstrap the 4.6 branch.
Rationale: fenv.h support will be present in cygwin 1.7.8 which is due
out any day now, and we didn't want to wait 6-8 months for the gcc-4.7
cycle in order to support decimal-floating-point stuff in cygwin/gcc.
You can install one of the more recent cygwin snapshots, and the build
should then work.
I do not understand the logic here: break GCC trunk for something that
hasn't been yet released.
Often new Cygwin version was announced as imminent and the true release
delayed for months..
(This time the announce was for 01 or 02 February.. and up today, 07,
nothing happened.)
GCC maintainers is this OK for your policy?
Angelo
