From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1
Date: Thu, 6 Mar 2008 14:56:54 -0800 (PST) [thread overview]
Message-ID: <20080306225654.2B0BE120183@busybox.net> (raw)
Author: jacmet
Date: 2008-03-06 14:56:50 -0800 (Thu, 06 Mar 2008)
New Revision: 21261
Log:
gcc 4.2.1: Don't change SUFFIX and bug report URL
SUFFIX and bug report URL shouldn't be set to something atmel specific
if you don't compile for AVR32.
The AVR32 patch should probably only get applied if compiling for AVR32.
Modified:
trunk/buildroot/toolchain/gcc/4.2.1/900-avr32-atmel.1.3.2.patch
Changeset:
Modified: trunk/buildroot/toolchain/gcc/4.2.1/900-avr32-atmel.1.3.2.patch
===================================================================
--- trunk/buildroot/toolchain/gcc/4.2.1/900-avr32-atmel.1.3.2.patch 2008-03-06 20:11:00 UTC (rev 21260)
+++ trunk/buildroot/toolchain/gcc/4.2.1/900-avr32-atmel.1.3.2.patch 2008-03-06 22:56:50 UTC (rev 21261)
@@ -20505,27 +20505,6 @@
// Bug: g++ was failing to destroy C<int>::a because it was using two
// different sentry variables for construction and destruction.
-diff -Nrup gcc-4.2.1/gcc/version.c gcc-4.2.1.atmel.1.3.2/gcc/version.c
---- gcc-4.2.1/gcc/version.c 2005-03-16 07:04:10.000000000 +0100
-+++ gcc-4.2.1.atmel.1.3.2/gcc/version.c 2007-09-28 10:33:09.000000000 +0200
-@@ -8,7 +8,7 @@
- in parentheses. You may also wish to include a number indicating
- the revision of your modified compiler. */
-
--#define VERSUFFIX ""
-+#define VERSUFFIX "-atmel.1.0.3"
-
- /* This is the location of the online document giving instructions for
- reporting bugs. If you distribute a modified version of GCC,
-@@ -17,7 +17,7 @@
- forward us bugs reported to you, if you determine that they are
- not bugs in your modifications.) */
-
--const char bug_report_url[] = "<URL:http://gcc.gnu.org/bugs.html>";
-+const char bug_report_url[] = "<URL:http://www.atmel.com/avr32/>";
-
- /* The complete version string, assembled from several pieces.
- BASEVER, DATESTAMP, and DEVPHASE are defined by the Makefile. */
diff -Nrup gcc-4.2.1/LAST_UPDATED gcc-4.2.1.atmel.1.3.2/LAST_UPDATED
--- gcc-4.2.1/LAST_UPDATED 2007-07-19 16:33:57.000000000 +0200
+++ gcc-4.2.1.atmel.1.3.2/LAST_UPDATED 1970-01-01 01:00:00.000000000 +0100
next reply other threads:[~2008-03-06 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 22:56 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-29 11:07 [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1 ulf at uclibc.org
2008-03-27 19:37 jacmet at uclibc.org
2007-10-17 21:56 ulf at uclibc.org
2007-08-30 6:00 ulf at uclibc.org
2007-08-28 18:21 ulf at uclibc.org
2007-08-25 11:22 aldot at uclibc.org
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=20080306225654.2B0BE120183@busybox.net \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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