Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Bryan Chua <chua@ayrnetworks.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: "George Gensure,,," <werkt@csh.rit.edu>, linux-mips@oss.sgi.com
Subject: Re: glibc build
Date: Fri, 20 Apr 2001 15:37:50 -0700	[thread overview]
Message-ID: <3AE0BA3E.A9D7658@ayrnetworks.com> (raw)
In-Reply-To: 20010420182053.A7282@bacchus.dhis.org

binutils 2.8.1, 2.9.1, 2.10, 2.10.1 (with and without patches) 2.11
gcc 2.95.2, 2.95.2.1, 2.95.3

The bug was that the specs file in 2.95.? seems to be missing a
-K__PIC__ in the spec for *cpp %{.S...}

It does seem to be in the current snapshot as of a few weeks ago and is
thus not necessary, but also not released.

-- bryan

Ralf Baechle wrote:

> On Fri, Apr 20, 2001 at 01:06:52PM -0700, Bryan Chua wrote:
>
> > CFLAGS=-D__PIC__ make all [check] install
> >
> > the target "check" will not work if you are cross compiling, so you
> > might as well install...  You end up coming across this in several
> > places.
>
> None of the compiler we ever recommended to use had this bug, so I
> wonder what compiler you're trying to use.
>
>   Ralf

  reply	other threads:[~2001-04-20 22:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20 19:14 glibc build George Gensure,,,
2001-04-20 20:06 ` Bryan Chua
2001-04-20 20:21   ` George Gensure
2001-04-20 20:21     ` George Gensure
2001-04-20 21:20   ` Ralf Baechle
2001-04-20 22:37     ` Bryan Chua [this message]
2001-04-30  9:28       ` Maciej W. Rozycki
  -- strict thread matches above, loose matches on Subject: below --
2001-04-20  5:14 George Gensure,,,
2001-04-20 18:55 ` Bryan Chua
2001-04-20 19:53   ` George Gensure
2001-04-20 19:53     ` George Gensure

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=3AE0BA3E.A9D7658@ayrnetworks.com \
    --to=chua@ayrnetworks.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    --cc=werkt@csh.rit.edu \
    /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