From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 6D3B1385841D; Mon, 10 Jun 2024 17:41:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6D3B1385841D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1718041281;
	bh=N553E21lXdcwXqsVQ3aE6ju1TkAJ7zT9LrmdVt7YIuM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=u1Hu0fjM8vtnV+nAuGrJWVtHyHQpDK2FCry1+Eb/m+qn9YqCPt5MAwZKqQO5Kfnf/
	 fap3B9ie7dpUOyaX7GmrHAse64zdDwyyk5pYqylZDu+n88cstoU7yXjOd5mOTBFPRM
	 J27+w6MpBT1OIxHuhbzx++ASDh0cfDZqxYN+OT4Q=
From: "syq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/115416] [13/14/15 regression] Setting --includedir to
 a nonexistent directory causes a build error since r13-5490-g59e4c98173a79f
Date: Mon, 10 Jun 2024 17:41:21 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: syq at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-115416-4-TFg2lkaiCx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-115416-4@http.gcc.gnu.org/bugzilla/>
References: <bug-115416-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D115416

--- Comment #6 from YunQiang Su <syq at gcc dot gnu.org> ---
(In reply to Marcus Calhoun-Lopez from comment #5)
> (In reply to YunQiang Su from comment #3)
> > Since it doesn't exist, why use --includedir with it?
>=20
> /opt/local/include/gcc is where the header files will be installed after =
the
> build, so there is no reason for it to exist before the build.
>=20

Normally, we build gcc for 1st stage with/without --includedir,=20
and then build libc with 1st stage gcc, and install the libc into the
destination.
Then we build gcc stage2 with --includedir.


Ohh, in fact that I am worrying that both you and I have a mistake: the
--includedir may be used for host instead of target.

Should we introduce a new build-time option?

Background: I add this patch due to Debian's cross toolchain install headers
into /usr/<triple>/include
instead of /usr/<triple>/sys-include=