From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89144 invoked by alias); 19 Nov 2019 00:11:11 -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 89130 invoked by uid 89); 19 Nov 2019 00:11:11 -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= X-HELO: esa4.mentor.iphmx.com Received: from esa4.mentor.iphmx.com (HELO esa4.mentor.iphmx.com) (68.232.137.252) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 19 Nov 2019 00:11:01 +0000 IronPort-SDR: sjbGf7+sJVE/ktuIBrNk7LAuZLCtTy/Gjc+jhcGZIQnJPrFObOu0AM9fAujaVRstYJXvPmcoda 6VX1nR0ZehhV8Y9uLz3CuCHWKnD0iyA6/47BlWhxttaH7K3UUe+wd5gljkcEFPyMILQFwH888M SjkVlsQFr/6ujLQN5P/9lbdNgXYEia3cso57QTm41L8aEP6ULenx4H68snZjRWZ8dmuzjJPiMX DhfchjiXioFRB24+DzDPEOExWu727nkVQ2BGR4EGVVXgu1CYHWyj87R5w8mIWy3JvI1NLCnbSI sXo= Received: from orw-gwy-01-in.mentorg.com ([192.94.38.165]) by esa4.mentor.iphmx.com with ESMTP; 18 Nov 2019 16:10:59 -0800 IronPort-SDR: txCVHsklChzezMaIS7vZgPnA8CFOGZxPRyoy2Ubzk0hTPQxKTK3el+/25Blp7mBquVc83cHgM1 AFMFm3KNOlx1zBmaH1CjTjRiO5bauent8pbRKwRc1OWjtmdmGhpguDD0vMHaBc3OaB8QHeV6UO 2pibYw0fN+YckJMDbjECP/VZ14I1PFUlZx+TdBBpTY00oyP5GeFfifhJr6QLAK8wZFxoMApF0H 9PQkoNJwKh+INw/b1a0TDGWbHt+dQnZ54C8W0pge2vPHBSdHHTVw6JAPc3RIsBdZ4MQfg5Gz7A Iyw= Date: Tue, 19 Nov 2019 00:11: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/msg00083.txt.bz2 On Mon, 18 Nov 2019, Maciej W. Rozycki wrote: > > 4. How does this interact with sysroot suffixes (again, this should be > > made clear in the documentation)? > > There is no interaction, the patch merely changes where the libraries are > installed. If the installation sysroot directory chosen is not one known > by the GCC driver, then the newly-installed target libraries won't be > automatically used (that of course can be changed with the appropriate use > of the `-B', `-L' and `--sysroot=' driver options). Perhaps the "sysroot" phrasing of the option name is confusing. The documentation in install.texi says "@var{dir} rather than @option{$@{gcc_tooldir@}/lib}". If that means, for example, that when "-print-multi-os-directory" prints "../lib64" the libraries are installed in $dir/../lib64 (so you'd pass --with-install-sysroot=/some/where/lib rather than --with-install-sysroot=/some/where), it's definitely not a sysroot. If in fact $dir/lib/../lib64 would be used, the documentation should say so. But even then, if you configure GCC using "--with-sysroot" or "--with-build-sysroot", both of those paths are the top-level sysroot, to which the sysroot suffix gets appended before GCC uses it for any purpose, unless you explicitly build using --no-sysroot-suffix. So I still think it's natural for a user of GCC's configure scripts to expect the new option, like the other sysroot-related configure options, also to be one to which the per-multilib sysroot suffix gets appended before GCC uses it. And if it's not like that, the documentation needs to say so explicitly. -- Joseph S. Myers joseph@codesourcery.com