public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aaro.koskinen at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63691] GCC 4.9.x fails to build GLIBC 2.20 on HPPA
Date: Fri, 31 Oct 2014 21:52:00 -0000	[thread overview]
Message-ID: <bug-63691-4-1RG53HKwtc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63691-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63691

--- Comment #8 from Aaro Koskinen <aaro.koskinen at iki dot fi> ---
(In reply to dave.anglin from comment #7)
> On 10/31/2014 2:39 PM, aaro.koskinen at iki dot fi wrote:
> > This patch is already included in GLIBC 2.20...
> I can add support for __builtin_trap() but we need preprocessed source
> and full compile command.  You can add "-save-temps -v" to glibc command
> to generate these files.

I was able to isolate the problem to GLIBC elf/dl-conflict.c and specifically
hppa specific elf_machine_rela function called from there. The problem occurs
at link time, so crafting a standalone preprocessed source file triggering the
error might be difficult, but I'll see what can I do.


  parent reply	other threads:[~2014-10-31 21:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 21:19 [Bug target/63691] New: " aaro.koskinen at iki dot fi
2014-10-30 21:27 ` [Bug target/63691] " aaro.koskinen at iki dot fi
2014-10-31  0:29 ` dave.anglin at bell dot net
2014-10-31  0:49 ` pinskia at gcc dot gnu.org
2014-10-31  1:18 ` pinskia at gcc dot gnu.org
2014-10-31 18:43 ` aaro.koskinen at iki dot fi
2014-10-31 19:43 ` dave.anglin at bell dot net
2014-10-31 21:52 ` aaro.koskinen at iki dot fi [this message]
2014-11-01  8:17 ` schwab@linux-m68k.org
2014-11-01 11:32 ` aaro.koskinen at iki dot fi
2014-11-01 14:34 ` danglin at gcc dot gnu.org
2014-11-04 19:36 ` aaro.koskinen at iki dot fi
2021-11-28 14:43 ` danglin at gcc dot gnu.org

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=bug-63691-4-1RG53HKwtc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).