Kai Tietz wrote:
2009/6/26 Seiji Kachi <ska...@mqe.biglobe.ne.jp>:
Angelo Graziosi wrote:
Dave Korn ha scritto:
Angelo Graziosi wrote:
I want to flag the following failure I have seen on Cygwin 1.5 trying to
build current 4.5-20090625 gcc snapshot:
So what's in config.log? And what binutils are you using?
The config logs are attached, while binutils is the current in Cygwin-1.5,
i.e. 20080624-2.
Cheers,
Angelo.
I have also seen similar faulure, and the reason on my environment is as
follows.
(1) In my case, gcc build complete successfully. But a.exe which is
compiled from the new compiler fails. Error message is
$ ./a.exe
bash: ./a.exe: Permission denied
Source code of a.exe is quite simple:
main()
{
printf("Hello\n");
}
(2) This failuer occurres from gcc trunk r148408. r148407 is OK.
(3) r148408 removed "#ifdef DEBUG_PUBTYPES_SECTION". r148407 does not
generate debug_pubtypes section, but r148408 and later version generates
debug_pubtypes section in object when we set debug option.
(4) gcc build sequence usually uses debug option.
(5) My cygwin environment seems not to accept debug_pubtypes section, and
pop up "Permission denied" error.
When I reverted "#ifdef DEBUG_PUBTYPES_SECTION" in dearf2out.c, the failuer
disappeared.
Does this failure occurr only on cygwin?
Regards,
Seiji Kachi
No, this bug appeared on all windows pe-coff targets. A fix for this
is already checked in yesterday on binutils. Could you try it with the
current binutils head version?
Cheers,
Kai
Is this supposed to be sufficient information for us to find that
binutils? I may be able to find an insider colleague, otherwise I would
have no chance.
