public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: aoliva@redhat.com
Cc: rth@redhat.com, gcc@gcc.gnu.org
Subject: Re: gcc 3.1 won't built along with binutils 2.12 on sparc-*-*
Date: Tue, 30 Apr 2002 16:24:00 -0000	[thread overview]
Message-ID: <20020430.160039.107127143.davem@redhat.com> (raw)
In-Reply-To: <orpu0hem93.fsf@free.redhat.lsd.ic.unicamp.br>

   From: Alexandre Oliva <aoliva@redhat.com>
   Date: 30 Apr 2002 03:25:28 -0300
   
   I suggest moving the test for .hidden into the `if x$gcc_cv_as != x'
   block, fixing the spelling of `-K PIC' and/or getting the code to
   tolerate assembler failures, and perhaps bumping up the version
   numbers in the version-based test for the case of builtin in a unified
   tree.

This has to be reimplemented for other reasons anyways (it is not
Sparc specific, this binutils problem, it turns out), see PR
target/6466 which is assigned to Richard currently.

      reply	other threads:[~2002-04-30 23:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30  0:18 Alexandre Oliva
2002-04-30 16:24 ` David S. Miller [this message]

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=20020430.160039.107127143.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=aoliva@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.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).