From: Kai Ruottu <kai.ruottu@wippies.com>
To: gcc-help@gcc.gnu.org, ">> Yaxuan Wen" <yw7013@nyu.edu>
Subject: Re: Errors in building gcc-4.4.3
Date: Thu, 18 Jan 2024 22:20:40 +0200 [thread overview]
Message-ID: <9f4fa5c9-297d-4bf4-9e3c-132a60d99fef@wippies.com> (raw)
In-Reply-To: <e0b09e9c-e945-4c90-84e8-8c84a403c19c@wippies.com>
Kai Ruottu kirjoitti 18.1.2024 klo 14.51:
>
> Kai Ruottu kirjoitti 18.1.2024 klo 14.39:
>> The prerequisites in your case are aworking compiler for
>> the'x86_64-linux' build system and a working cross-compiler from the
>> build/host 'x86_64-linux' system to the target 'x86_64-nacl-linux'
>> system. Whether the GCC configure scripts could quess what tools the
>> build should use for the $host and $target I have no clue. Years I
>> have always defined these with the : AR=<something> \ CC= <something>
>> \ CXX=<something> \ .... RANLIB=<something> \ for the $host system.
>> And : AR_FOR_TARGET=<something> \ CC_FOR_TARGET= <something> \
>> CXX_FOR_TARGET=<something> \ .... RANLIB_FOR_TARGET=<something> \ for
>> the $target system. Similarly for the $build system with the :
>> <TOOL>_FOR_BUILD=<something> rows in the script used as the
>> configure command, before the final 'configure' command in it.
>> Not much left to guess...
>>
> Should I now shoot Thunderbird because it decided to change my written
> text to something unreadable?
Maybe not... Let's try again via copy&paste using Notepad to "normalize"
whatever there was in the Thunderbird text...
---------- clip ----------
The prerequisites in your case are a working compiler for the
'x86_64-linux' build system and
a working cross-compiler from the build/host 'x86_64-linux' system to
the target 'x86_64-nacl-linux' system.
Whether the GCC configure scripts could quess what tools the build
should use for the $host
and $target I have no clue. Years I have always defined these with the :
AR=<something> \
CC= <something> \
CXX=<something> \
....
RANLIB=<something> \
for the $host system. And :
AR_FOR_TARGET=<something> \
CC_FOR_TARGET= <something> \
CXX_FOR_TARGET=<something> \
....
RANLIB_FOR_TARGET=<something> \
for the $target system. Similarly for the $build system with the :
<TOOL>_FOR_BUILD=<something> rows in the script used as the
configure command, before the final 'configure' command in it.
Not much left to guess...
---------- clip ----------
prev parent reply other threads:[~2024-01-18 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 23:23 Yaxuan Wen
2024-01-18 12:39 ` Kai Ruottu
2024-01-18 12:51 ` Kai Ruottu
2024-01-18 20:20 ` Kai Ruottu [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=9f4fa5c9-297d-4bf4-9e3c-132a60d99fef@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=gcc-help@gcc.gnu.org \
--cc=yw7013@nyu.edu \
/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).