From: "David S. Miller" <davem@caip.rutgers.edu>
To: gas2@cygnus.com
Subject: Binutils-2.5.2 on SGI-irix4
Date: Sat, 04 Mar 1995 15:05:00 -0000 [thread overview]
Message-ID: <199503042305.SAA29569@firefox.rutgers.edu> (raw)
A local friend provided this bug report for me. I hope you find it
useful in some way.
----------------------------------------------------------------
Date: Sat, 4 Mar 1995 17:57:09 -0500
From: Adrian Rodriguez <adrian@romulus.rutgers.edu>
You may want to pass this on to your friends at Cygnus.
Software: Binutils 2.5.2
Source: ftp://prep.ai.mit.edu/pub/gnu/binutils-2.5.2.tar.gz
Host: SGI Indigo
OS: Irix 4.0.5F
Bug: configure forces use of cc
Description:
It appears that there is no way to use gcc to build binutils short of
changing the definition of CC in binutils-2.5.2/config/mh-irix4. The
configure script provided ignores the environment variable CC and the
command line options --with-gcc and --with-gnu-c. Binutils will not
build with the version of SGI's C compiler on this machine. I want to
do this because SGI's compiler barfs on targ-cpu.c with errors I can
provide if you are interested.
reply other threads:[~1995-03-04 15:05 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=199503042305.SAA29569@firefox.rutgers.edu \
--to=davem@caip.rutgers.edu \
--cc=gas2@cygnus.com \
/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).