From: Adrian Bunk <bunk@stusta.de>
To: Jeff Dike <jdike@addtoit.com>
Cc: torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [PATCH 4/9] UML - Export gcov symbol based on gcc version
Date: Fri, 11 Mar 2005 17:55:26 +0100 [thread overview]
Message-ID: <20050311165526.GA3723@stusta.de> (raw)
In-Reply-To: <200503111849.j2BImsJp003370@ccure.user-mode-linux.org>
On Fri, Mar 11, 2005 at 01:48:54PM -0500, Jeff Dike wrote:
> bunk@stusta.de said:
> > This patch is still wrong.
> > It seems my comment on this [1] was lost:
> > <-- snip -->
> > This line has to be something like
> > ( (__GNUC__ == 3 && __GNUC_MINOR__ == 3 && __GNUC_PATCHLEVEL__ >= 4)
> > && \
> > HEAVILY_PATCHED_SUSE_GCC )
>
> > I hope SuSE has added some #define to distinguish what they call "gcc
> > 3.3.4" from GNU gcc 3.3.4
>
> It wasn't lost - I am just disinclined to cater to distros making their
> gcc lie about its version.
And therefore you added a patch that helps only those distros at the
price of breaking other people and distros using sane compilers?
> Jeff
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-03-11 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 2:16 [PATCH 4/9] UML - Export gcov symbol based on gcc version Jeff Dike
2005-03-10 22:53 ` Adrian Bunk
2005-03-10 23:21 ` Linus Torvalds
2005-03-11 17:00 ` [uml-devel] " Blaisorblade
2005-03-11 18:47 ` Jeff Dike
2005-03-11 17:01 ` [uml-devel] " Blaisorblade
2005-03-11 18:48 ` Jeff Dike
2005-03-11 16:55 ` Adrian Bunk [this message]
2005-03-11 17:00 ` [uml-devel] " stian
2005-03-11 23:53 ` Jeff Dike
2005-03-11 23:37 ` Adrian Bunk
2005-03-12 3:45 ` Jeff Dike
2005-03-11 19:35 ` [uml-devel] " Blaisorblade
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=20050311165526.GA3723@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=user-mode-linux-devel@lists.sourceforge.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