public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "00pebuis at bsu dot edu" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/61005] New: libgcj.spec openned when not needed (-S on command line) Date: Tue, 29 Apr 2014 17:39:00 -0000 [thread overview] Message-ID: <bug-61005-8172@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61005 Bug ID: 61005 Summary: libgcj.spec openned when not needed (-S on command line) Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: java Assignee: unassigned at gcc dot gnu.org Reporter: 00pebuis at bsu dot edu I get a libgcj.spec "no such file or directory" error message when cross-compiling on an x86 linux host with an ARM target. I'm using the -S option to emit assembly code and *not* converting to .o or linking. The libgcj.spec file describes how to link, so is unnedeed. It would seem to me that if -S is specified on the command it is just asking for trouble to attempt to open this .spec file. Of course, the *real* problem is in my Linux distro which didn't provide the needed .spec file for cross-compiling.
next reply other threads:[~2014-04-29 17:39 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-29 17:39 00pebuis at bsu dot edu [this message] 2014-04-29 17:57 ` [Bug java/61005] " pinskia at gcc dot gnu.org 2014-04-29 18:00 ` schwab@linux-m68k.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-61005-8172@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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).