From: "H . J . Lu" <hjl@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] The 1117 snapshot cpp problem
Date: Mon, 05 Feb 2001 19:57:31 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005114@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205880@msgid-missing>
On Wed, Jan 24, 2001 at 01:37:24PM -0800, Jim Wilson wrote:
> >I guess it is a long standing issue in the Cygnus toolchain. The
> >problem is this change:
> >Bascallly, it sets local_prefix = prefix, which means
> >$local_prefix/include = $prefix/include
>
> >Now, gcc will search /usr/include before others. It is not very good
> >for Linux.
>
> Yes, this is a problem.
>
> I've reverted the Cygnus local change in my source tree, and have started
> working to get the same change into the main Cygnus source tree. This will
> require changing some local build processes, so it may take a little time.
>
> There is no problem with cross compilers as you suggested, because cross
> compilers don't use /usr/local/include. I believe the original problem was
> that we shipped compilers to some customers that had random files in
> /usr/local, the customers reported problems, and we had a lot of trouble
> debugging the problem. We fixed it by deciding not to use /usr/local/include
> by default anymore. This was 8 years ago, so Linux usage was not a concern.
> Now that we are part of Red Hat, it is a serious concern.
>
> The resulting patch is 100K because configure had to be rebuilt. I put it
> in the usual place, ftp.cygnus.com:/pub/ia64-linux/snap-001117/patch.055.
>
I don't think it works with the gnupro rpm from RedHat. I had to
add the patch enclosed here. I think the problem is includedir in gcc
is overriden from the toplevel Makefile.
--
H.J. Lu (hjl@valinux.com)
---
--- gcc/Makefile.in.local Thu Jan 4 15:21:25 2001
+++ gcc/Makefile.in Thu Jan 4 15:22:00 2001
@@ -292,7 +292,7 @@ build_tooldir = $(exec_prefix)/$(target_
# Directory in which the compiler finds g++ includes.
gcc_gxx_include_dir= @gcc_gxx_include_dir@
# Directory to search for site-specific includes.
-includedir = $(local_prefix)/include
+localincludedir = $(local_prefix)/include
# assertdir is overridden in cross-make.
# (But this currently agrees with what is in cross-make.)
assertdir = $(gcc_tooldir)/include
@@ -1881,7 +1881,7 @@ intl.distdir-fixup:
PREPROCESSOR_DEFINES = \
-DGCC_INCLUDE_DIR=\"$(libsubdir)/include\" \
-DGPLUSPLUS_INCLUDE_DIR=\"$(gcc_gxx_include_dir)\" \
- -DLOCAL_INCLUDE_DIR=\"$(includedir)\" \
+ -DLOCAL_INCLUDE_DIR=\"$(localincludedir)\" \
-DCROSS_INCLUDE_DIR=\"$(gcc_tooldir)/sys-include\" \
-DTOOL_INCLUDE_DIR=\"$(gcc_tooldir)/include\"
@@ -2447,7 +2447,7 @@ installdirs:
if [ -d $${fdir} ] ; then true ; else mkdir $${fdir}; chmod a+rx $${fdir}; fi ; \
done
-if [ -d $(bindir) ] ; then true ; else mkdir $(bindir) ; chmod a+rx $(bindir) ; fi
- -if [ -d $(includedir) ] ; then true ; else mkdir $(includedir) ; chmod a+rx $(includedir) ; fi
+ -if [ -d $(localincludedir) ] ; then true ; else mkdir $(localincludedir) ; chmod a+rx $(localincludedir) ; fi
-if [ -d $(gcc_tooldir) ] ; then true ; else mkdir $(gcc_tooldir) ; chmod a+rx $(gcc_tooldir) ; fi
-if [ -d $(assertdir) ] ; then true ; else mkdir $(assertdir) ; chmod a+rx $(assertdir) ; fi
-if [ -d $(infodir) ] ; then true ; else mkdir $(infodir) ; chmod a+rx $(infodir) ; fi
next prev parent reply other threads:[~2001-02-05 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 17:46 [Linux-ia64] The 1117 snapshot cpp problem H . J . Lu
2001-01-24 21:37 ` Jim Wilson
2001-02-05 19:57 ` H . J . Lu [this message]
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-105590693005114@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