From: Allan Clark <chickenandporn@gmail.com>
To: Zibri <zibri@zibri.org>
Cc: crossgcc@sourceware.org
Subject: Re: g++ is not compiled?!
Date: Wed, 28 Feb 2018 14:57:00 -0000 [thread overview]
Message-ID: <92B5464B-D6C8-4F9A-8B06-1316883E0730@gmail.com> (raw)
In-Reply-To: <9da70dad-e1ad-4072-8408-aea0f83c95b1@zibri.org>
> On Feb 28, 2018, at 3:22 AM, Zibri <zibri@zibri.org> wrote:
...
>
> It did everything correct but there is no arm g++ in the x-tools directory!
>
> What should I do?
Include details in your request for help: links to: configure used, “find” command output where you think the binary should be created, etc. details we can read and consider.
Make it easier to help you by not having to ask for each of the details we’ll probably need to look at.
prev parent reply other threads:[~2018-02-28 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 11:22 Zibri
2018-02-28 14:57 ` Allan Clark [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=92B5464B-D6C8-4F9A-8B06-1316883E0730@gmail.com \
--to=chickenandporn@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=zibri@zibri.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).