public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Tietz <ktietz70@googlemail.com>
To: tprince@computer.org
Cc: Seiji Kachi <skachi@mqe.biglobe.ne.jp>,
	Angelo Graziosi <angelo.graziosi@alice.it>,
	 	Dave Korn <dave.korn.cygwin@googlemail.com>,
	Fortran <fortran@gcc.gnu.org>,  	GCC <gcc@gcc.gnu.org>
Subject: Re: Failure building current 4.5 snapshot on Cygwin
Date: Fri, 26 Jun 2009 16:28:00 -0000	[thread overview]
Message-ID: <90baa01f0906260917h28b4137fi730656b212ce16ab@mail.gmail.com> (raw)
In-Reply-To: <4A44EC02.60003@sbcglobal.net>

2009/6/26 Tim Prince <TimothyPrince@sbcglobal.net>:
> Kai Tietz wrote:
>>
>> 2009/6/26 Seiji Kachi <skachi@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.
>

Hello,

you can find the binutils project as usual under
http://sources.redhat.com/binutils/ . You can find on this page how
you are able to get current cvs version of binutils. This project
contains the gnu tools, like dlltool, as, objcopy, ld, etc.
The issue you are running in is reasoned by a failure in binutils
about setting correct section flags for debugging sections. By the
last change in gcc - it was the output of the .debug_pubtypes secton -
this issue was shown.
There is a patch already applied to binutils's repository head, which
should solve the issue described here in this thread. We from
mingw-w64 were fallen already over this issue and have taken care.

Cheers,
Kai

-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

  reply	other threads:[~2009-06-26 16:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 11:18 Angelo Graziosi
2009-06-26 11:42 ` Dave Korn
2009-06-26 13:09   ` Angelo Graziosi
2009-06-26 13:19     ` Seiji Kachi
2009-06-26 13:52       ` Kai Tietz
2009-06-26 15:59         ` Tim Prince
2009-06-26 16:28           ` Kai Tietz [this message]
2009-06-26 16:36             ` Steve Kargl
2009-06-26 17:01               ` Angelo Graziosi
2009-06-26 17:06                 ` Steve Kargl
2009-06-26 17:29             ` Tim Prince
2009-06-27  0:55         ` Seiji Kachi
2009-08-23  6:45           ` Eric Niebler
2009-08-23 10:16             ` Ralf Wildenhues
2009-08-23 22:26             ` Eric Niebler
2009-06-26 15:41   ` Tim Prince
2009-06-26 14:33 ` Tim Prince
2009-08-23 14:20 Angelo Graziosi
2009-08-23 17:57 ` Eric Niebler
2009-08-23 18:08   ` Tim Prince
2009-08-23 19:59     ` Eric Niebler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=90baa01f0906260917h28b4137fi730656b212ce16ab@mail.gmail.com \
    --to=ktietz70@googlemail.com \
    --cc=angelo.graziosi@alice.it \
    --cc=dave.korn.cygwin@googlemail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=skachi@mqe.biglobe.ne.jp \
    --cc=tprince@computer.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).