From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1040 invoked by alias); 22 Nov 2019 23:54:58 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 1030 invoked by uid 89); 22 Nov 2019 23:54:58 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=sk:no-sysr, sk:nosysr X-HELO: esa2.mentor.iphmx.com Received: from esa2.mentor.iphmx.com (HELO esa2.mentor.iphmx.com) (68.232.141.98) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 22 Nov 2019 23:54:57 +0000 IronPort-SDR: cvLJp6Tz2oiRvTQbRlfN3zfn6Lc4QYNkpojTqAwO8G58qvtK1xs0YV6OzXWLsVdbAC2+jI05kQ AWUa/BWlsy0lL6eQuU2li6j48+Jd9hREupwqykrbHCFrMvaGQnL0LPneJr5nTBg2Ene2bLaqvG yQTIMuvy4q6ZwdqRNqkLDqu4d4NN0+urjNc8cgI+/qlPjjQI3dbNr+eUhm6td8Wsp/4Usean7Z dolNj6onCD1v+A/8uX63ROOUjvcPumHNLn7hsTeU8IP3tDT9H+mx+N5P0ecHx9urzuXMy6Bk2U VUs= Received: from orw-gwy-01-in.mentorg.com ([192.94.38.165]) by esa2.mentor.iphmx.com with ESMTP; 22 Nov 2019 15:54:55 -0800 IronPort-SDR: HFWykClDnUDZIoOrcKFa9fNpY7Hiczb7KAU2PgYGSMSkgeQ0YryAbsNJSN/9i2FhZoRcNlHHZ3 Hz+CHLRdZoe8J916wBJiYfvLHudUADuFvHWzm+iRi4ovokI2Mubo3xrzDH1R++NB977BUkJtic Ec1HMEtEwADikfOS6UZiH1bWOTN80YPOeAUx+mO/V172CEw7CMiFRXGvuqRQKvOBVGl3EJgZ4W MXi3WymRjo/np+sfpvnsSBkr9D0oofTolvobo2OktSy0f0OV7W4orzQUu9e27sukLHEzObmAoI 6uk= Date: Fri, 22 Nov 2019 23:54:00 -0000 From: Joseph Myers To: "Maciej W. Rozycki" CC: , , , Subject: Re: [PATCH v2] Add `--with-install-sysroot=' configuration option In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-Path: joseph@codesourcery.com X-SW-Source: 2019/txt/msg00087.txt.bz2 On Fri, 22 Nov 2019, Maciej W. Rozycki wrote: > As I recall the MIPS sysroot setup (please correct me if I got something > wrong here) was like: Yes, that's the sort of layout you get with sysroot suffixes. See gcc/config/mips/{st.h,t-st} for an example. > Then the right-hand side of /path/to/somewhere (except for usr/) is what > gets printed by `-print-multi-directory' or the left-hand side of output > from `-print-multi-lib', e.g. `sof/el/lib64' for the example above. Rather, it's a suffix (as in SYSROOT_SUFFIX_SPEC, no command-line option to print it), followed by a directory such as /lib64 that comes from STARTFILE_PREFIX_SPEC. (Until MULTILIB_OSDIRNAMES / -print-multi-os-directory were added, I think STARTFILE_PREFIX_SPEC was the main mechanism for using directories such as /lib64; once the multilib OS directory mechanism was added, STARTFILE_PREFIX_SPEC was needed much less, but is still relevant for this sysroot use case, along with some linker configuration in binutils to teach it about such directories.) > Similarly `-print-multi-os-directory' prints a directory path relative to > a lib/ subdirectory to the sysroot, so that would be `../sof/el/lib64' > respectively. Rather, it's a path relative to the (non-sysroot, before your patch) directory where the compiler installs the libraries. See e.g. t-st using paths such as ../lib64/2f. > Well, I agree we need to have this stuff documented beyond what we > currently have, but I think it applies equally to all the sysroot options > we have, including both the `--sysroot=' GCC driver's option, and the > `--with-sysroot=', `--with-build-sysroot=' and the newly-proposed All three of those refer to the top-level sysroot path, to which a sysroot suffix is appended based on SYSROOT_SUFFIX_SPEC (unless --no-sysroot-suffix is used). > `--with-install-sysroot=' `configure' script's options as well. All we > currently have is this paragraph: But this is a path relative to which SYSROOT_SUFFIX_SPEC isn't used at all. > And last but not least: do we want to hold my proposed change hostage to > a sysroot handling documentation improvement? It does not appear fair to > me as the situation with said documentation is not a new problem nor one > specific to this newly-added option, and the new option merely played the The proposed new option is, as far as I know, the first one introducing this new kind of sysroot option (one for which the suffix from SYSROOT_SUFFIX_SPEC is never added). -- Joseph S. Myers joseph@codesourcery.com