From: Tommy Murphy <tommy_murphy@hotmail.com>
To: "crossgcc@sourceware.org" <crossgcc@sourceware.org>,
Arwa Ghaith <arwagheith80@gmail.com>
Subject: Re: building gcc cross compiler failed
Date: Thu, 21 Dec 2023 17:32:41 +0000 [thread overview]
Message-ID: <LO0P123MB49551A63D479093154D68D0BF995A@LO0P123MB4955.GBRP123.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAMNT4j8xABNYdNEm0z7oOTqfx4nsZJOVy6Q87k3_dbq4XxR03A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
Might be better to post an issue here with all of the info requested by the "New Issue" form:
* https://github.com/crosstool-ng/crosstool-ng/issues
At a glance I cannot see any error or failure in the log that you posted so you might want to clarify what exactly the problem is that you're encountering.
prev parent reply other threads:[~2023-12-21 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 17:21 Arwa Ghaith
2023-12-21 17:32 ` Tommy Murphy [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=LO0P123MB49551A63D479093154D68D0BF995A@LO0P123MB4955.GBRP123.PROD.OUTLOOK.COM \
--to=tommy_murphy@hotmail.com \
--cc=arwagheith80@gmail.com \
--cc=crossgcc@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).