public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Frederic.Petrot@lip6.fr To: gcc-gnats@gcc.gnu.org Subject: other/4753: Gcc fails to build libgcc for mips target on linux host Date: Wed, 31 Oct 2001 04:16:00 -0000 [thread overview] Message-ID: <20011031121134.25772.qmail@sourceware.cygnus.com> (raw) >Number: 4753 >Category: other >Synopsis: Gcc fails to build libgcc for mips target on linux host >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Oct 31 04:16:02 PST 2001 >Closed-Date: >Last-Modified: >Originator: Frederic.Petrot@lip6.fr >Release: 3.0.2 >Organization: >Environment: Linux redhat 7.2 >Description: Gcc fails to build libgcc for a mips target, on any host I suppose. It cannot find fp-bit.c and dp-bit.c that seems not to be copied into the objdir/gcc when running configure (or at some other time, I'm really not sure). >How-To-Repeat: ~/gcc-3.0.2/ is gcc tarball untared (srcdir) ~/gcc/ is objdir ~/gcc $ ~/gcc-3.0.2/configure --prefix=$HOME/bin --with-gnu-as --with-gnu-ld --target=mipsel-cass-ecoff --disable-multi-lib --disable-threads --enable-language=c --disable-libgcj ~/gcc $ make >Fix: cp ~/gcc-3.0.2/gcc/[fd]-bit.c ~/gcc/gcc But this is not a reasonnable one ;) >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-10-31 4:16 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=20011031121134.25772.qmail@sourceware.cygnus.com \ --to=frederic.petrot@lip6.fr \ --cc=gcc-gnats@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).