From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) by sourceware.org (Postfix) with ESMTPS id C5D58385BF83 for ; Sun, 12 Apr 2020 16:06:30 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org C5D58385BF83 Received: by mail-lf1-x129.google.com with SMTP id u10so3667389lfo.8 for ; Sun, 12 Apr 2020 09:06:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MHj+tSxyBTPc7xZZQw5RfZCg6opJrKoXtTSwVcw80mk=; b=bMM5BPYX3diG0+yDJjDOGOsG0nb+Xg2zTzSsSF8wwAejfMBVDLtUJkxhV1M0sye3bE NqG22LF+HdVWfekDtU4KpVVzfwY8Sjqk5JCU1c+q+bFL28cmbJvODf0syfeibCkhnQ5C EzDGiiaUxOAW3lRyLKKE+/ygn/emJmb2KjdAL+F2DmEgEDTkfT6qLqSVgxmVQlXBQS+F Vc3f+PP9kDOdKhM+1hoD/xUWRvRRk1iz5PSCQHle3C35BqIH1jTVWI5KpscYSb20BLDn WPpSBG4gZXDVsUdden6DY+/QWiw2tDQVqye3DnnVKMLeJQ37nYd7FDs7U13NbpXfFP2D DtTQ== X-Gm-Message-State: AGi0PuZ1fjlRHxZRhM1/jygoQGNMgU3E1GC6BwYbx3s61lTABleEIt66 zfLeW65XPIg3yurz/hd9KKdw2jn/P9kHdKvyCKY= X-Google-Smtp-Source: APiQypKwkXtl4fR4DG6SFNVmDLg8Bvek6E8CvGjpgMpIXjEJ/XEF70QAeEqF0tw7rjI9ySUp2HyeBiAIUnRa9OFe7LU= X-Received: by 2002:a19:c3c5:: with SMTP id t188mr8319981lff.199.1586707589464; Sun, 12 Apr 2020 09:06:29 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: William Tambe Date: Sun, 12 Apr 2020 12:06:17 -0400 Message-ID: Subject: Re: How to customize GCC builtin search paths To: Jim Wilson Cc: gcc-help Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2020 16:06:33 -0000 On Fri, Apr 10, 2020 at 1:16 PM Jim Wilson wrote: > > On Thu, Apr 9, 2020 at 7:52 PM William Tambe via Gcc-help > wrote: > > How to customize GCC builtin search paths that it uses for %s in its > > specs syntax ? > > This is startfile_prefixes in gcc.c. I can hardly find examples on how to use startfile_prefixes. Currently when running gcc as follow: arch-elf-gcc -v test.c I get the following excerpt showing how gcc looks for includes: #include "..." search starts here: #include <...> search starts here: /opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/include /opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/include-fixed /opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/../../../../arch-elf/include However, I am looking to change how gcc looks for includes as follow: #include "..." search starts here: #include <...> search starts here: /opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/../../../../include /opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/../../../../arch-elf/include /opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/include /opt/arch-toolchain/lib/gcc/arch-elf/9.2.0/include-fixed Any idea what piece of code populate the list of paths where to look for includes ? > > Jim