public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13555] New: Remove configure.in support for old targets
Date: Tue, 03 Jan 2012 22:21:00 -0000	[thread overview]
Message-ID: <bug-13555-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=13555

             Bug #: 13555
           Summary: Remove configure.in support for old targets
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper.fsp@gmail.com
        ReportedBy: jsm28@gcc.gnu.org
    Classification: Unclassified


glibc's configure.in has support for several architectures not supported in
libc or ports any more

a29k | am29000) base_machine=a29k machine=a29k ;;
c3[012])        base_machine=cx0 machine=cx0/c30 ;;
c4[04])         base_machine=cx0 machine=cx0/c40 ;;
m88???)         base_machine=m88k machine=m88k/$machine ;;
m88k)           base_machine=m88k machine=m88k/m88100 ;;

and a similar case over $os, where gnu* and linux* are the only OSes that can
actually be used now.  The cases for no-longer-supported architectures and OSes
should be removed.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-01-03 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 22:21 jsm28 at gcc dot gnu.org [this message]
2012-01-07 16:14 ` [Bug libc/13555] " drepper.fsp at gmail dot com
2014-06-27 11:16 ` fweimer at redhat dot 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=bug-13555-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.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).