This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.2.2 release notes, third draft
- From: Christian Cornelssen <ccorn at cs dot tu-berlin dot de>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: Joe Buck <jbuck at synopsys dot com>,Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, <gcc at gcc dot gnu dot org>
- Date: Wed, 5 Feb 2003 14:39:30 +0100 (CET)
- Subject: Re: gcc 3.2.2 release notes, third draft
Hi,
On 5 Feb 2003, Alexandre Oliva wrote:
> On Feb 4, 2003, Christian Cornelssen <ccorn@cs.tu-berlin.de> wrote:
>
> >> 3.2.2 is a bug fix release only; there are no new features that were
> >> not present in GCC 3.2.1.
>
> > This appears to be true as long as those "features" are attributed
> > to the to-be-built-and-installed software only. However, the 3.2.2
> > build system now supports DESTDIR completely and thus simplifies the
> > synopsis of packaging commands.
>
> It was a bug-fix, though. Sub-packages of GCC that used automake
> already had partial support for DESTDIR. It was incomplete, though,
> and your patch fixed that. That's the only reason why I even
> considered proposing to merge the patch into 3.2. If it were really a
> new feature, it probably shouldn't have gone in.
Yep, and I wouldn't have made it if there had not been a common
feeling that it should be supported. However, I ususally associate
"bug" with something that has been specified (or implied) to work
before, and didn't do so. If that's the way you want to look at it,
the announcements of DESTDIR support in both `gcc-3.2/changes.html'
and `gcc-3.3/changes.html' have to be changed such that they do not
appear as "miscelleanous improvements" (3.2) or as an item in
"other significant improvements" (3.3), but as regular bug fixes:
<li>Redirecting a top-level <code>make install</code> by setting the
<code>make</code> variable <code>DESTDIR</code> now works.</li>
And the announcements as of
http://gcc.gnu.org/ml/gcc-patches/2003-01/msg02299.html
and
http://gcc.gnu.org/ml/gcc-patches/2003-01/msg02204.html
should be removed.
Regards,
Christian Cornelssen