From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: Re: Error building power-pc-unknown-linux-gnu toolchain
Date: Thu, 02 Feb 2017 20:10:00 -0000 [thread overview]
Message-ID: <7c75edb7-4da9-3a47-18a3-b9ec1bbf5b6f@att.net> (raw)
In-Reply-To: <CAHZxF5wdMCksOgiU=s57O-Zcaqee70CAVTaY2c7XEPzSN_QkAw@mail.gmail.com>
Please report the issue on Github [1], and attach the .config file that
you were using.
[1] https://github.com/crosstool-ng/crosstool-ng/issues
Regards,
Alexey.
On 02/02/2017 12:01 PM, Khernel Panik wrote:
> Good afternoon,
>
> After building crosstool-ng from the latest git master, and attempting
> to build a toolchain for powerpc-unknown-linux-gnu, I'm running into
> an error during the "Building gdbserver" step:
>
> [INFO ] Installing gdbserver
> [EXTRA] Configuring gdbserver
> [EXTRA] Building gdbserver
> [ERROR] /home/callpop/toolchains/ppc32be/.build/src/gdb-7.12/gdb/gdbserver/../nat/ppc-linux.h:22:26:
> fatal error: asm/cputable.h: No such file or directory
> [ERROR] make[1]: *** [linux-ppc-low.o] Error 1
> [ERROR] make[1]: *** Waiting for unfinished jobs....
>
> I didn't see anything about this particular error in the known issues
> document, and the only place on my filesystem that I can find the file
> it's looking for is definitely outside of the .build directory. Is
> this a missing file, or perhaps a misconfiguration on my part? Since
> the lib and include directories are in place, I think I can move
> forward as I am attempting to use clang and just needed the libraries
> and headers, but it would be nice to chase this one down in the case
> that I need gdbserver.
>
> Thanks,
>
> - KP
>
prev parent reply other threads:[~2017-02-02 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 20:01 Khernel Panik
2017-02-02 20:10 ` Alexey Neyman [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=7c75edb7-4da9-3a47-18a3-b9ec1bbf5b6f@att.net \
--to=stilor@att.net \
--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).