On Wed, 9 Aug 2023, Arsen Arsenović via Gcc-patches wrote: > Joseph Myers <jos...@codesourcery.com> writes: > > > On Tue, 8 Aug 2023, Arsen Arsenović via Gcc-patches wrote: > > > >> Yes. Libtool was forked over a decade ago. My next project is syncing > >> upstream and us back up. Unsure about pkg.m4. > > > > Note as per previous discussions that libtool commit > > 3334f7ed5851ef1e96b052f2984c4acdbf39e20c will need reverting in GCC when > > updating libtool because of incompatible usage of --with-sysroot. > > I wanted to, somehow, coalesce the two back together, so that both are > available. Presumably, this means adding an option to libtool to accept > host-sysroot or such, but I haven't done too much looking into this. > > Is my interpretation of the issue correct? (i.e. GCC uses sysroot to > mean *target* sysroot rather than host sysroot)
GCC's sysroot is a sysroot containing target headers and libraries, yes. Also note: * The --with-sysroot directory is the directory that would be used by GCC if installed in the configured --prefix (relocated if GCC ends up running from a different prefix). At build time, --with-build-sysroot takes precedence. * The --with-sysroot directory (and likewise the --with-build-sysroot directory or any directory specified with --sysroot= passed to GCC programs) may sometimes contain multiple sysroots in subdirectories; that directory gets combined with a suffix from SYSROOT_SUFFIX_SPEC to determine the actual subdirectory for the current multilib, within which there are subdirectories such as usr/include or usr/lib. -- Joseph S. Myers jos...@codesourcery.com
