From: 欧阳春晖 <jack9603301@163.com>
To: Xi Ruoyao <xry111@xry111.site>,
Dingjun Chen <Dingjun.Chen@geotechairborne.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: FW: For help!
Date: Tue, 14 Nov 2023 21:14:57 +0800 [thread overview]
Message-ID: <b43d1843-65f6-444d-a3a1-88df1e0e94d3@163.com> (raw)
In-Reply-To: <059865dc35aa592632c6688f898faf6b982e46f0.camel@xry111.site>
Of course, in addition to LFS, if you are willing to spend time
exploring, you can also consider referring to Gentoo's Crossdev script.
However, there is essentially no difference - LFS is just a template.
Obviously, its method is universal. You can arbitrarily select any part
of the compilation process, for example, the cross-compiler build
command - you only need to modify some parameters and refer to the
configure command help. If you want to use automated tools, you can also
use third-party tools to compile the cross-compilation environment
> On Tue, 2023-11-14 at 21:00 +0800, 欧阳春晖 via Gcc-help wrote:
>> I think you should ensure that the compiler of your cross-compilation
>> environment meets the minimum requirements for compiling a
>> cross-compiler. The consequences of forcibly bypassing version detection
>> may be more errors. For the specific cross-compilation process, you can
>> refer to the Linux From Scratch documentation. description of.
> No. Stop. I personally added the following note into LFS several years
> ago:
>
> The LFS book is not (and does not contain) a general tutorial to build a
> cross- (or native) toolchain. Don't use the commands in the book for a
> cross-toolchain for some purpose other than building LFS, unless you
> really understand what you are doing.
>
>
> It's just off-topic and annoying to ask all these questions about
> building these ancient software via gcc-help. And it's also off-topic
> with LFS. Please try to ask via a "retro-computing" forum instead.
>
prev parent reply other threads:[~2023-11-14 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 12:33 Dingjun Chen
2023-11-14 12:40 ` FW: " Dingjun Chen
2023-11-14 12:54 ` 欧阳春晖
[not found] ` <e9a4723f-17fb-4514-bc51-178d357ac388@163.com>
2023-11-14 12:57 ` Dingjun Chen
2023-11-14 13:00 ` 欧阳春晖
2023-11-14 13:08 ` Xi Ruoyao
2023-11-14 13:10 ` 欧阳春晖
2023-11-14 13:14 ` 欧阳春晖 [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=b43d1843-65f6-444d-a3a1-88df1e0e94d3@163.com \
--to=jack9603301@163.com \
--cc=Dingjun.Chen@geotechairborne.com \
--cc=gcc-help@gcc.gnu.org \
--cc=xry111@xry111.site \
/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).