From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) by sourceware.org (Postfix) with ESMTPS id 034A03870847 for ; Thu, 7 May 2020 10:43:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 034A03870847 Received: by mail-il1-x12d.google.com with SMTP id c16so760283ilr.3 for ; Thu, 07 May 2020 03:43:14 -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:content-transfer-encoding; bh=6GclMZaQcT3Cm7ATS2jtcn2Tap5FRpU0A8dII8rNLpw=; b=at7m0OIPw6YIA/kOtM6ixnDzS8Qn0wsUYIxlGKlt8aYg+CqlP5+nmNZPWS2Oun8lMS fBck3FzkyvX/osUmvD1/u/kHXQqh5cUS1Pp2PPGlhdIi25abR3fRKYNxAocbamQtYFOT AsMJezbIqvxy8uIWZC3NS17s463WGJNDzZvkPSMvcLM4X2FuO3GuQBVcntTA7anvJ/yz RKfuiDmOyKzx31GpLm/K7Hlr7ZCaDKCFiKDa0N0NfpCbk6bPcNEUveb5E+M0d9o6LPSM RXPNrGaGK80srow++kSjakaRHtT0WhJXyN7NZJZAX4lCvfR78z8NXuFWAS4rUuivzI2T q15Q== X-Gm-Message-State: AGi0PuYUsdSgR1uDJhPwTPMPfjpjh1ZAIGmqYIlsW/4DCnWxeuTlw7Cq ZHNCUmH7+9cS8ai3YvO9hbn0DqALLRv74FCL54o= X-Google-Smtp-Source: APiQypJVCFBUiAmQbJXtDffmGa9Z+zA7z0oFSxuZJxFQDinBWWej3Wht/l4SQnNw13vnObLZSj+jw+cyZVtFv6IrRF0= X-Received: by 2002:a92:5f55:: with SMTP id t82mr14191040ilb.261.1588848194038; Thu, 07 May 2020 03:43:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Thu, 7 May 2020 11:43:03 +0100 Message-ID: Subject: Re: Building a compiler that honors symbolic links. To: xaxazak xak Cc: gcc-help Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-3.0 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: Thu, 07 May 2020 10:43:25 -0000 On Thu, 7 May 2020 at 09:46, xaxazak xak via Gcc-help wrote: > > When I manually build GCC (via SVN trunk) or LLVM (via GIT trunk) I > use a symbolic link (/make/) to my development folder as part of the > destination path. > > Both GCC and LLVM extract the =E2=80=9Cphysical=E2=80=9D target location = of this > symlink, so their default include paths etc use the physical location, > which starts with (/media///...) instead of just > (/make/...). > > This is annoying for a few reasons: > > 1. I=E2=80=99m capturing the header information (via -H), and I want to a= void > having and included in this list. > 2. can change. > > I can choose to not use the default include paths (eg -nostdinc++ > etc), and just explicitly set them when I invoke clang, but that makes > build setup a lot more complex. > > Is there any way I can build GCC (and LLVM / clang if you know) so > that it remembers my symlinks instead of expanding them? You'll have to provide more information. How are you configuring GCC? What are the paths involved? What is the path you're talking about used for? Is it where GCC is installed? --prefix? --with-sysroot? Something else? What paths does gcc show if you add -v when compiling?