From: Peter Bergner <bergner@vnet.ibm.com>
To: dclarke@blastwave.org
Cc: Anthony Green <green@moxielogic.com>,
kyle.d.moffett@boeing.com, libffi-discuss@sourceware.org
Subject: Re: libffi fails to build on powerpc64-linux
Date: Tue, 06 Mar 2012 16:17:00 -0000 [thread overview]
Message-ID: <1331050603.21041.25.camel@otta> (raw)
In-Reply-To: <50878.10.0.66.17.1331007647.squirrel@interact.purplecow.org>
On Mon, 2012-03-05 at 23:20 -0500, Dennis Clarke wrote:
> I am no where near my powermac g5 but as soon as I can I'll climb back
> in and see what I can get done with libffi. The entire objective of my
> efforts was to get a clean bootstrap of GCC 4.6.2 for ppc970 and then
> to work towards GCC 4.7.0RC1 etc. Thus this is a bit of a road block
> that must be cleared on ppc.
I just built mainline libffi on my G5 installed with Fedora 16 which has
GCC 4.6.2 installed. Building went fine (using my latest patch from my
other email) and so did the testsuite run.
I'll mention that Fedora 16's GCC defaults to producing 64-bit binaries.
Are you trying to build libffi on a system where GCC defaults to producing
32-bit binaries and you're trying to produce a 64-bit libffi?
Peter
next prev parent reply other threads:[~2012-03-06 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 4:21 Dennis Clarke
2012-03-06 16:17 ` Peter Bergner [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-09 2:37 David Edelsohn
2012-03-09 8:02 ` Kyle Moffett
2012-03-07 4:13 Dennis Clarke
2012-03-05 23:05 Dennis Clarke
2012-03-05 23:29 ` Peter Bergner
2012-03-06 0:29 ` Peter Bergner
2012-03-06 3:18 ` Anthony Green
2012-03-06 15:36 ` Peter Bergner
2012-03-06 16:16 ` Peter Bergner
2012-03-07 4:03 ` Peter Bergner
2012-03-08 23:14 ` Peter Bergner
2012-03-09 1:01 ` Peter Bergner
2012-03-05 22:56 Peter Bergner
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=1331050603.21041.25.camel@otta \
--to=bergner@vnet.ibm.com \
--cc=dclarke@blastwave.org \
--cc=green@moxielogic.com \
--cc=kyle.d.moffett@boeing.com \
--cc=libffi-discuss@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).