From: Dennis Clarke <dclarke@blastwave.org>
To: Anthony Green <green@moxielogic.com>
Cc: Peter Bergner <bergner@vnet.ibm.com>,
kyle.d.moffett@boeing.com, libffi-discuss@sourceware.org,
dclarke@blastwave.org
Subject: Re: libffi fails to build on powerpc64-linux
Date: Tue, 06 Mar 2012 04:21:00 -0000 [thread overview]
Message-ID: <50878.10.0.66.17.1331007647.squirrel@interact.purplecow.org> (raw)
> (let me preface this by apologizing for the build breakage)
>
> On Mon, Mar 5, 2012 at 7:28 PM, Peter Bergner <bergner@vnet.ibm.com> wrote:
>> Taking my best swag at where the soft_double_prep label should be
>> (comment said it should be handled like UINT64), I tried the following
>> patch which allows everything to build without warnings and seems to
>> pass the testsuite:
>>
>>
>> Â Â Â Â Â Â Â Â === libffi Summary ===
>>
>> # of expected passes       1659
>> # of unsupported tests      55
>
> Those results look fine, however, the soft_double_prep label was
> specifically removed by this patch...
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=powerpc-ffi-softfloat.patch;att=1;bug=644338
>
> ...which was designed to enable support for soft-float ppc targets,
> among other things. I see now that the original patch didn't remove
> all references to soft_double_prep.
>
> At this point, I'm hoping that Kyle Moffett, the author of this patch
> can have a look. My guess is that either I mis-applied the patch, or
> he posted the wrong patch to apply.
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.
Dennis
--
--
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B
+-------------------------+-----------------------------------+
| Dennis Clarke | Solaris and Linux and Open Source |
| dclarke@blastwave.org | Respect for open standards. |
+-------------------------+-----------------------------------+
next reply other threads:[~2012-03-06 4:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 4:21 Dennis Clarke [this message]
2012-03-06 16:17 ` Peter Bergner
-- 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=50878.10.0.66.17.1331007647.squirrel@interact.purplecow.org \
--to=dclarke@blastwave.org \
--cc=bergner@vnet.ibm.com \
--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).