public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tangyilei10 at itp dot ac.cn" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/60059] New: Error when building gcc-4.8.2 together with binutils 2.24 Date: Tue, 04 Feb 2014 16:08:00 -0000 [thread overview] Message-ID: <bug-60059-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60059 Bug ID: 60059 Summary: Error when building gcc-4.8.2 together with binutils 2.24 Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: tangyilei10 at itp dot ac.cn I'm building gcc-4.8.2 with binutils extracted in the source directory. After I made dir gcc-build as a build dir, configured it and typed make, error came out. The error indicates that the system was unable to acquire ar in directory binutils. So I went into the binutils directory inside the gcc-build and typed ln -sv binutils/ar ar cd .. make The make goes on while it reported it could not find ranlib, so I again go into the binutils directory and typed ln -sv binutils/ranlib ranlib cd .. make The make goes on while it was bothered again reporting that the nm in the directory gcc returned the wrong message, so I just cd gcc mv nm nm_backup ln -sv ../binutils/binutils/nm-new nm cd .. make and the make goes on. As it worked in every stage, the previously compiled binutils and gcc are wiped off so these tricks should be repeated 2 times. I think it is the bug because you misunderstood the structure of the tarball of the binutils. Any way, my trick seems to work well.
reply other threads:[~2014-02-04 16:08 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-60059-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: linkBe 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).