public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97865] libtool needs to be updated for Darwin20.
Date: Tue, 17 Nov 2020 22:09:17 +0000 [thread overview]
Message-ID: <bug-97865-4-wpv8xBivZ4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97865-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865
--- Comment #13 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to joseph@codesourcery.com from comment #12)
> config.sub and config.guess are imported, unmodified, from upstream
> config.git.
thanks I will try to do that and test it over the next days (I've been using a
newish version on arm64-darwin20 for a few months so don't anticipate problems
- but who knows).
> libtool has lots of local changes, hopefully all of them submitted
> upstream but maybe not and maybe some not committed upstream (libtool has
> very few commits in recent years, but lots since the 2009 version used in
> GCC). As well as checking all the local changes (relative to libtool
> commit 2c9c38d8a12eb0a2ce7fe9c3862523026c3d5622, apparently) and applying
> them to a new version as needed, updating libtool would also require
> reverting libtool commit 3334f7ed5851ef1e96b052f2984c4acdbf39e20c to deal
> with a mismatch of --with-sysroot interpretations.
The patch I have here is a additional local change (and specific to Darwin),
unfortunately, I don't have resources to address the scope of work you
describe.
next prev parent reply other threads:[~2020-11-17 22:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 20:49 [Bug target/97865] New: MACOSX_DEPLOY_TARGET needs to be updated juergen.reuter at desy dot de
2020-11-16 21:12 ` [Bug target/97865] " egallager at gcc dot gnu.org
2020-11-16 21:56 ` juergen.reuter at desy dot de
2020-11-17 9:58 ` iains at gcc dot gnu.org
2020-11-17 10:12 ` juergen.reuter at desy dot de
2020-11-17 10:32 ` iains at gcc dot gnu.org
2020-11-17 10:36 ` juergen.reuter at desy dot de
2020-11-17 10:49 ` iains at gcc dot gnu.org
2020-11-17 13:05 ` iains at gcc dot gnu.org
2020-11-17 14:04 ` juergen.reuter at desy dot de
2020-11-17 21:23 ` iains at gcc dot gnu.org
2020-11-17 21:24 ` iains at gcc dot gnu.org
2020-11-17 22:02 ` [Bug target/97865] libtool needs to be updated for Darwin20 joseph at codesourcery dot com
2020-11-17 22:09 ` iains at gcc dot gnu.org [this message]
2020-11-18 8:39 ` juergen.reuter at desy dot de
2020-11-18 19:31 ` iains at gcc dot gnu.org
2020-11-19 11:00 ` juergen.reuter at desy dot de
2020-11-19 11:37 ` juergen.reuter at desy dot de
2020-11-19 12:53 ` iains at gcc dot gnu.org
2020-11-19 12:57 ` iains at gcc dot gnu.org
2020-11-19 13:01 ` iains at gcc dot gnu.org
2020-11-19 13:10 ` iains at gcc dot gnu.org
2020-11-19 16:12 ` iains at gcc dot gnu.org
2020-11-19 19:50 ` juergen.reuter at desy dot de
2020-11-19 23:46 ` iains at gcc dot gnu.org
2020-11-25 20:49 ` iains at gcc dot gnu.org
2020-12-03 9:49 ` juergen.reuter at desy dot de
2020-12-03 9:53 ` iains at gcc dot gnu.org
2020-12-05 13:25 ` cvs-commit at gcc dot gnu.org
2020-12-06 18:41 ` juergen.reuter at desy dot de
2021-01-03 9:28 ` cvs-commit at gcc dot gnu.org
2021-05-01 13:08 ` cvs-commit at gcc dot gnu.org
2021-05-17 8:08 ` jakub at gcc dot gnu.org
2021-10-01 23:11 ` iains at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-97865-4-wpv8xBivZ4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).