From: Jeff Johnston <jjohnstn@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: newlib@sourceware.org
Subject: Re: [PATCH htdocs] faq: update cross-compiler entry
Date: Wed, 3 Jan 2024 18:05:35 -0500 [thread overview]
Message-ID: <CAOox84tDne3EtOSR7Mi5+19Jtn=Zu+cHT5hGDiS2aDOoZ0RN2A@mail.gmail.com> (raw)
In-Reply-To: <20231221004853.3256-1-vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Patch applied. Thanks.
-- Jeff J.
On Wed, Dec 20, 2023 at 7:49 PM Mike Frysinger <vapier@gentoo.org> wrote:
> 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
>
>
prev parent reply other threads:[~2024-01-03 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 0:48 Mike Frysinger
2024-01-03 23:05 ` Jeff Johnston [this message]
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='CAOox84tDne3EtOSR7Mi5+19Jtn=Zu+cHT5hGDiS2aDOoZ0RN2A@mail.gmail.com' \
--to=jjohnstn@redhat.com \
--cc=newlib@sourceware.org \
--cc=vapier@gentoo.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).