From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] gcc: add patches for powerpc e6500 64-bit support
Date: Fri, 6 Nov 2015 17:05:09 +0100 [thread overview]
Message-ID: <563CCFB5.4040109@mind.be> (raw)
In-Reply-To: <1446818745-32224-1-git-send-email-arnout@mind.be>
On 06-11-15 15:05, Arnout Vandecappelle (Essensium/Mind) wrote:
> Building with -mtune=e6500 led to build failures in glibc (probably in
> uclibc as well) because gcc was built for a 32-bit target even though
> the target tuple is powerpc64-*. This lead to a mix of 32-bit and
> 64-bit support and build errors like:
>
> fatal error: gnu/lib-names-32.h: No such file or directory
>
> The root cause is that the configure script is not handling e6500
> correctly, because of stupid typo in the condition.
>
> Change has been submitted upstream.
Patch has been accepted upstream.
Regards,
Arnout
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Alvaro Gamez <alvaro.gamez@hazent.com>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-11-06 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 14:05 [Buildroot] [PATCH 1/2] gcc: add patches for powerpc e6500 64-bit support Arnout Vandecappelle
2015-11-06 14:05 ` [Buildroot] [PATCH 2/2] arch: add tune options for powerpc e5500 and e6500 Arnout Vandecappelle
2015-11-10 15:09 ` Alvaro Gamez
2015-11-16 23:17 ` Peter Korsgaard
2015-11-06 16:05 ` Arnout Vandecappelle [this message]
2015-11-16 23:16 ` [Buildroot] [PATCH 1/2] gcc: add patches for powerpc e6500 64-bit support Peter Korsgaard
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=563CCFB5.4040109@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.