public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/63539] New: libgo does not use the newly built objcopy when doing a combined build
Date: Wed, 15 Oct 2014 02:09:00 -0000	[thread overview]
Message-ID: <bug-63539-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 63539
           Summary: libgo does not use the newly built objcopy when doing
                    a combined build
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: go
          Assignee: ian at airs dot com
          Reporter: pinskia at gcc dot gnu.org
                CC: cmang at google dot com

I was trying build a go compiler for aarch46 and ran into this issue.

I was doing a full combined build with all of GCC/binutils from the trunk.

f=`echo container/ring.lo | sed -e 's/.lo$/.o/'`; objcopy -j .go_export $f
container/ring.gox.tmp && mv -f container/ring.gox.tmp container/ring.gox
objcopy: Unable to recognise the format of the input file `container/ring.o'


In this case container/ring.o is an aarch64 elf binary and my host objcopy
(2.20) does not understand aarch64 elf files.


             reply	other threads:[~2014-10-15  2:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15  2:09 pinskia at gcc dot gnu.org [this message]
2014-10-15  2:25 ` [Bug go/63539] " pinskia at gcc dot gnu.org
2014-10-15  2:26 ` pinskia at gcc dot gnu.org
2014-10-15  6:10 ` pinskia at gcc dot gnu.org
2014-10-15  6:13 ` pinskia at gcc dot gnu.org
2014-11-23  4:21 ` [Bug bootstrap/63539] " pinskia at gcc dot gnu.org
2015-01-03 22:51 ` pinskia at gcc dot gnu.org
2015-01-03 22:51 ` pinskia 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-63539-4@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).