From: Jeff Dike <jdike@karaya.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.7pre8aa1
Date: Thu, 19 Jul 2001 20:42:50 -0400 [thread overview]
Message-ID: <200107200042.f6K0goP09224@karaya.com> (raw)
In-Reply-To: Your message of "Fri, 20 Jul 2001 03:37:49 +0200." <20010720033749.J31850@athlon.random>
andrea@suse.de said:
> works fine thanks! Of course I agree with rmk it would be better not
> to disable -fno-common but this is ok for now ;)
Yeah, it's temporary. rmk's idea was to use the link script to toss errno.o
out of the final binary.
> (after all we would
> catch any potential important name collision during the compiles of
> the other targets)
Agreed. -fno-common is definitely good. The only conflict is errno, but
when Arjan first started playing with -fno-common, he found a couple of UML
bugs.
Jeff
next prev parent reply other threads:[~2001-07-20 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 22:45 2.4.7pre8aa1 Jeff Dike
2001-07-20 1:37 ` 2.4.7pre8aa1 Andrea Arcangeli
2001-07-20 0:42 ` Jeff Dike [this message]
2001-07-23 1:11 ` 2.4.7pre8aa1 Andrea Arcangeli
2001-07-23 3:49 ` 2.4.7pre8aa1 Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2001-07-19 18:38 2.4.7pre8aa1 Andrea Arcangeli
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=200107200042.f6K0goP09224@karaya.com \
--to=jdike@karaya.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.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