From: Daniel Jacobowitz <drow@false.org>
To: Anmol Paralkar-B07584 <b07584@freescale.com>
Cc: gdb@sourceware.org
Subject: Re: Need current information for (old) --with-cpu flag in configure.in.
Date: Thu, 22 Feb 2007 04:09:00 -0000 [thread overview]
Message-ID: <20070221220204.GA19029@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702211523340.10056@ld0159-tx32.am.freescale.net>
On Wed, Feb 21, 2007 at 03:57:05PM -0600, Anmol Paralkar-B07584 wrote:
> Hello,
>
> (I am working on gdb-6.6). In rs6000-tdep.c, we have the comment:
> (Above the line: static struct variant variants[] =)
>
> /* ...
>
> If you add entries to this table, please be sure to allow the new
> value as an argument to the --with-cpu flag, in configure.in. */
>
> However, the "--with-cpu" flag is missing in gdb-6.6/configure.in.
>
> Please could you let me know the change intended here to any of the
> configure scripts when adding a new cpu?
To be honest, I have no idea what that comment is referring to.
--with-cpu only affects GCC, not GDB.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-21 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 22:22 Anmol Paralkar-B07584
2007-02-22 4:09 ` Daniel Jacobowitz [this message]
2007-02-22 11:49 ` Michael Snyder
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=20070221220204.GA19029@caradoc.them.org \
--to=drow@false.org \
--cc=b07584@freescale.com \
--cc=gdb@sourceware.org \
/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