From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27387 invoked by alias); 7 Apr 2003 13:16:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 27359 invoked by uid 71); 7 Apr 2003 13:16:01 -0000 Date: Mon, 07 Apr 2003 13:16:00 -0000 Message-ID: <20030407131601.27357.qmail@sources.redhat.com> To: zack@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Daniel Jacobowitz Subject: Re: preprocessor/8505: cross cpp0 use PREFIX_INCLUDE_DIR=$prefix/include Reply-To: Daniel Jacobowitz X-SW-Source: 2003-04/txt/msg00258.txt.bz2 List-Id: The following reply was made to PR preprocessor/8505; it has been noted by GNATS. From: Daniel Jacobowitz To: Zack Weinberg Cc: benoit.poulot-cazajou@jaluna.com, stephane.carbillet@jaluna.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: preprocessor/8505: cross cpp0 use PREFIX_INCLUDE_DIR=$prefix/include Date: Mon, 7 Apr 2003 09:09:51 -0400 On Thu, Apr 03, 2003 at 05:05:20PM -0800, Zack Weinberg wrote: > > [http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8505] > > My apologies for letting this go for so long. > > I am not expert in the domain of cross compilers, and I can think of > plausible reasons both to have the PREFIX_INCLUDE_DIR searched and > not to have it searched. It would be consistent with what is done > for other directories, like LOCAL_INCLUDE_DIR, not to search it; > however, it appears that this directory has been searched in cross > compilers since forever, so people might be depending on the existing > behavior. > > I would appreciate opinions. Dan, I'm cc:ing you because you've had > your fingers in this area recently. If you look at 3.4, you'll see the test has changed: if test x$with_sysroot = x && test x$host = x$target \ && test "$prefix" != "/usr" && test "x$prefix" != "x$local_prefix" ; then AC_DEFINE_UNQUOTED(PREFIX_INCLUDE_DIR, "$prefix/include") fi i.e. cross compilers no longer search $prefix/include/. I'm sre it'll break someone's setup somewhere; however, it also just makes more sense this way. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer