Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: schwab@suse.de
Cc: gcc@gcc.gnu.org, binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Overlapping patterns in toplevel configure.in
Date: Tue, 09 Apr 2002 06:28:00 -0000	[thread overview]
Message-ID: <200204091328.g39DSJF21858@envy.delorie.com> (raw)
In-Reply-To: <jeofgt5k0r.fsf@sykes.suse.de> (message from Andreas Schwab on Tue, 09 Apr 2002 10:55:00 +0200)


> The toplevel congfigure.in script contains a case pattern *-*-linux* that
> overrules the pattern mips*-*-linux*.  The first pattern only exists in
> the gcc repository, not in the src repository.  There are also other linux
> cases that are not a superset of the generic *-*-linux* case.  What is the
> best way to resolve that?  Perhaps the generic linux pattern should be
> moved to a separate case statement.  But there is also a catch-all
> pattern at the end that disables libgcj for all not explicitly mentioned
> targets unless --enable-libgcj is given.  In other words, it's a big
> mess. :-(

I'm currently working on syncing the toplevel files between gcc and
src, so at least please wait until I finish that, or at least make
sure both sides get updated.  Otherwise, simply rearranging the
patterns so that the more specific ones come first makes sense;
perhaps put all the chip-independent patterns at the end?


      parent reply	other threads:[~2002-04-09 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09  1:55 Andreas Schwab
2002-04-09  2:26 ` Thiemo Seufer
2002-04-09  2:34   ` Andreas Schwab
2002-04-09  6:28 ` DJ Delorie [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=200204091328.g39DSJF21858@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=schwab@suse.de \
    /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