From: Leonidas Spyropoulos <artafinde@gmail.com>
To: crossgcc@sourceware.org
Cc: artafinde@gmail.com
Subject: CT-NG error while building for RPi armv7
Date: Sun, 15 May 2016 10:28:00 -0000 [thread overview]
Message-ID: <20160515102832.p3dkg3fpbwifiveo@tiamat> (raw)
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
Hello,
I'm trying to build crosstool-ng in Archlinux x86-64 machine to help my
RPi compile packages using distcc (following the [1]) During the process
it fails with:
[EXTRA] Building C library
[ERROR] setenv.c:279:6: error: suggest explicit braces to avoid
ambiguous 'else' [-Werror=dangling-else]
[ERROR] make[3]: ***
[/home/inglor/cross/bin/.build/arm-unknown-linux-gnueabihf/build/build-libc-final/stdlib/setenv.o]
Error 1
[ERROR] make[2]: *** [stdlib/subdir_lib] Error 2
[ERROR] make[1]: *** [all] Error 2
I'm attaching the build logs.
Anyone can give some hints?
CC me on the responses I'm not the mailing list.
[1]: https://archlinuxarm.org/wiki/Distcc_Cross-Compiling
--
Leonidas Spyropoulos
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
[-- Attachment #2: build.log.tar.gz --]
[-- Type: application/octet-stream, Size: 1379670 bytes --]
[-- Attachment #3: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-05-15 10:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160515102832.p3dkg3fpbwifiveo@tiamat \
--to=artafinde@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).