From: mod+linuxppc-dev@MissionCriticalLinux.com
To: linuxppc-dev@lists.linuxppc.org
Subject: [PATCH] Link-time failures from "simple" CFLAGS changes
Date: Mon, 07 Jan 2002 17:23:09 -0500 [thread overview]
Message-ID: <200201072223.RAA06381@missioncriticallinux.com> (raw)
Sheesh! Well, OK then: please apply this patch:
===== Documentation/Changes 1.12 vs edited =====
--- 1.12/Documentation/Changes Fri Dec 7 14:01:21 2001
+++ edited/Documentation/Changes Mon Jan 7 17:20:20 2002
@@ -92,6 +92,8 @@
greater than -O2 may not be wise. Similarly, if you choose to use gcc-2.95.x
or derivatives, be sure not to use -fstrict-aliasing (which, depending on
your version of gcc 2.95.x, may necessitate using -fno-strict-aliasing).
+On the other hand, -O0 will cause your build to fail because inline
+functions are only defined when *some* optimization is in effect.
Make
----
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-01-07 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 22:23 mod+linuxppc-dev [this message]
2002-01-07 23:00 ` [PATCH] Link-time failures from "simple" CFLAGS changes Tom Rini
2002-01-07 23:28 ` mod+linuxppc-dev
2002-01-08 0:21 ` Tom Rini
2002-01-08 23:03 ` Paul Mackerras
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=200201072223.RAA06381@missioncriticallinux.com \
--to=mod+linuxppc-dev@missioncriticallinux.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).