From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Cc: Nathanael Nerode <neroden@doctormoo.dyndns.org>
Subject: Re: PATCH: autoconfiscate SPU
Date: Mon, 28 Jan 2002 19:26:00 -0000 [thread overview]
Message-ID: <20020128222633.A21541@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0201282149360.28159-100000@nerodeguest>
On Mon, Jan 28, 2002 at 09:50:14PM -0500, Nathanael Nerode wrote:
> This patch autoconfiscates SPU. (Directory src/utils/spu)
> It's a pretty basic job, not actually working around any potentially
> missing headers, but it works (on i686-linux-gnu, debian woody)
>
> Because 'configure' is new, cvs diff refused to mention it. It's generated
> by autoconf 2.50 from configure.in and will need to be committed along
> with the patch.
>
> Because of this and the total changes to the other two files, the patch
> looks far worse than the three files; if anyone wants me to wrap those up
> somehow, I will.
>
> 2002-01-28 Nathanael Nerode <neroden@twcny.rr.com>
> Autoconfiscation of SPU.
> * utils/spu/configure: new file for autoconfiscation
> * utils/spu/configure.in: replaced for autoconfiscation
> * utils/spu/Makefile.in: replaced for autoconfiscation
> ! AC_PREREQ([2.50])
No.
The entire remainder of the tree uses autoconf 2.13. It is not yet
autoconf aware. Moving to autoconf 2.5 is a relatively short-term
goal, but for now any configure.in's you add MUST work with 2.13.
Working with 2.5 is a plus.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-01-29 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 18:50 Nathanael Nerode
2002-01-28 19:26 ` Daniel Jacobowitz [this message]
2002-01-29 7:35 ` PATCH: autoconfiscate SPU (take two) Nathanael Nerode
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=20020128222633.A21541@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@doctormoo.dyndns.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