public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: [PATCH htdocs] faq: update cross-compiler entry
Date: Wed, 20 Dec 2023 19:48:53 -0500	[thread overview]
Message-ID: <20231221004853.3256-1-vapier@gentoo.org> (raw)

The crossgcc site hasn't been hosted on sthoward.com in decades.
It moved to a diff site long ago, but even that stopped working
a while ago.  Send people to the crosstool-ng project as that is
the current standard in this space (and has been for quite a while
too).
---
 faq.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/faq.html b/faq.html
index 0aabe168bed1..79e027d62bb9 100644
--- a/faq.html
+++ b/faq.html
@@ -43,7 +43,8 @@ make all-target-newlib.
 <p>
 <a name="q3"></a>
 <li>I want to have newlib built with gcc and other components from the net.  How do I do this?
-<p>For cross-compilation info, check out <a href=http://www.sthoward.com/CrossGCC/>the crossgcc faq</a>.  When setting up a unified source directory, remember
+<p>For cross-compilation info, check out <a href="https://crosstool-ng.github.io/">the crosstool-NG project</a>.
+When setting up a unified source directory, remember
 that the newlib subdirectory should be a sibling to gcc, binutils, etc..  All
 of these net projects share a top-level directory so you only want to copy or
 link the tools/libraries subdirectories specifically.  For example, the newlib
-- 
2.43.0


             reply	other threads:[~2023-12-21  0:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21  0:48 Mike Frysinger [this message]
2024-01-03 23:05 ` Jeff Johnston

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=20231221004853.3256-1-vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=newlib@sourceware.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).