public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Dennis Clarke <dclarke@blastwave.org>
To: Peter Bergner <bergner@vnet.ibm.com>
Cc: libffi-discuss@sourceware.org, Anthony Green <green@moxielogic.com>
Subject: Re: libffi fails to build on powerpc64-linux
Date: Mon, 05 Mar 2012 23:05:00 -0000	[thread overview]
Message-ID: <64185.10.0.66.17.1330988704.squirrel@interact.purplecow.org> (raw)


> After the latest libffi merge into GCC, GCC no longer builds on
> powerpc64-linux due to the following errors:

I ran into a bucket of issues with libffi also :

  http://sourceware.org/ml/libffi-discuss/2012/msg00048.html

May or may not be related.

dc



-- 
--
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.       |
+-------------------------+-----------------------------------+

             reply	other threads:[~2012-03-05 23:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 23:05 Dennis Clarke [this message]
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
  -- 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-06  4:21 Dennis Clarke
2012-03-06 16:17 ` 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=64185.10.0.66.17.1330988704.squirrel@interact.purplecow.org \
    --to=dclarke@blastwave.org \
    --cc=bergner@vnet.ibm.com \
    --cc=green@moxielogic.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).