public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "inaoka.kazuhiro@renesas.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/10978] New: [m32r-elf] miss install crtini.o crtfini.o for m32rx target. Date: Mon, 26 May 2003 05:57:00 -0000 [thread overview] Message-ID: <20030526053448.10978.inaoka.kazuhiro@renesas.com> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10978 Summary: [m32r-elf] miss install crtini.o crtfini.o for m32rx target. Product: gcc Version: 3.3 Status: UNCONFIRMED Severity: normal Priority: P2 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: inaoka.kazuhiro@renesas.com CC: gcc-bugs@gcc.gnu.org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: m32r-elf Crtini.o and crtfini.o for m32rx target are built, but not installed. sample file: hello.c int main() { return 0; } command line: m32r-elf-gcc -m32rx hello.c status log: /usr/local/m32r-org/lib/gcc-lib/m32r-elf/3.3/../../../../m32r-elf/bin/ld: cannot open m32rx/crtinit.o: No such file or directory collect2: ld returned 1 exit status The following was a patch:(on gcc-3.2.3) http://gcc.gnu.org/ml/gcc-patches/2003-04/msg01202.html ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2003-05-26 5:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-26 5:57 inaoka.kazuhiro@renesas.com [this message] 2003-05-26 6:42 ` [Bug target/10978] " dhazeghi@yahoo.com 2003-05-26 10:54 ` inaoka.kazuhiro@renesas.com 2003-05-26 14:43 ` pinskia@physics.uc.edu 2003-06-01 2:57 ` bangerth@dealii.org 2003-06-02 11:49 ` nickc@redhat.com 2003-06-02 17:38 ` dhazeghi@yahoo.com 2003-06-03 8:52 ` nickc@redhat.com 2003-06-03 10:36 ` dhazeghi@yahoo.com
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=20030526053448.10978.inaoka.kazuhiro@renesas.com \ --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).