From: "H . J . Lu" <hjl@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] The 1117 snapshot cpp problem
Date: Fri, 05 Jan 2001 17:46:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205880@msgid-missing> (raw)
My email sent to ia64-tools@napali.hpl.hp.com went to a black hole :-).
I tried it again here.
H.J.
----- Forwarded message from "H . J . Lu" <hjl@valinux.com> -----
Date: Thu, 4 Jan 2001 14:26:30 -0800
From: "H . J . Lu" <hjl@valinux.com>
To: ia64-tools@napali.hpl.hp.com
Subject: The 1117 snapshot cpp problem.
User-Agent: Mutt/1.2.5i
I guess it is a long standing issue in the Cygnus toolchain. The
problem is this change:
--- gcc/configure.in Fri Dec 22 13:55:48 2000
+++ gcc/configure.in Thu Aug 17 12:02:45 2000
@@ -136,15 +136,17 @@ AC_ARG_WITH(elf,
elf="$with_elf",
elf=no)
-# Specify the local prefix
-local_prefix-AC_ARG_WITH(local-prefix,
-[ --with-local-prefix=DIR specifies directory to put local include.],
-[case "${withval}" in
-yes) AC_MSG_ERROR(bad value ${withval} given for local include directory prefix) ;;
-no) ;;
-*) local_prefix=$with_local_prefix ;;
-esac])
+# CYGNUS LOCAL: local_prefix
+#local_prefix+#AC_ARG_WITH(local-prefix,
+#[ --with-local-prefix=DIR specifies directory to put local include.],
+#[case "${withval}" in
+#yes) AC_MSG_ERROR(bad value ${withval} given for local include directory prefix) ;;
+#no) ;;
+#*) local_prefix=$with_local_prefix ;;
+#esac])
+local_prefix='$(prefix)'
+# END CYGNUS LOCAL
# Default local prefix if it is empty
if test x$local_prefix = x; then
Bascallly, it sets local_prefix = prefix, which means
$local_prefix/include = $prefix/include
It is ok and desirable for a cross toolchain as long as you don't
install it under /usr as a native compiler. Unfortunately, RedHat/ia64
does exactly that. That means $local_prefix/include = /usr/include.
Now, gcc will search /usr/include before others. It is not very good
for Linux.
# touch l.c
# gcc -M -v l.c
Reading specs from /usr/lib/gcc-lib/ia64-redhat-linux/2.96-ia64-000717/specs
gcc version 2.96-ia64-000717 snap 001117
/usr/lib/gcc-lib/ia64-redhat-linux/2.96-ia64-000717/cpp ...
GNU CPP version 2.96-ia64-000717 snap 001117 (cpplib)
(IA-64)
ignoring duplicate directory "/usr/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/include
/usr/lib/gcc-lib/ia64-redhat-linux/2.96-ia64-000717/include
/usr/ia64-redhat-linux/include
End of search list.
l.o: l.c
H.J.
----- End forwarded message -----
next reply other threads:[~2001-01-05 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 17:46 H . J . Lu [this message]
2001-01-24 21:37 ` [Linux-ia64] The 1117 snapshot cpp problem Jim Wilson
2001-02-05 19:57 ` H . J . Lu
2001-02-06 12:56 ` Andreas Schwab
2001-02-07 7:06 ` H . J . Lu
2001-02-08 0:20 ` Jim Wilson
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=marc-linux-ia64-105590678205880@msgid-missing \
--to=hjl@valinux.com \
--cc=linux-ia64@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