From: Matthias Klose <doko@ubuntu.com>
To: Anthony Green <green@moxielogic.com>,
libffi-discuss <libffi-discuss@sourceware.org>
Subject: Re: libffi 3.3 release candidate 1
Date: Wed, 27 Nov 2019 07:54:00 -0000 [thread overview]
Message-ID: <816931f1-7ff7-60bf-82c1-e2221b1ec1dd@ubuntu.com> (raw)
In-Reply-To: <CACxje5-QCKEYV0d3=+AmkYq02HX1Zr21rwSnM15YRwDk6Oo1ig@mail.gmail.com>
On 24.10.19 13:16, Anthony Green wrote:
> libffi 3.3 release candidate 1 is available for testing...
>
> https://github.com/libffi/libffi/releases/download/v3.3-rc1/libffi-3.3-rc1.tar.gz
> https://github.com/libffi/libffi/releases/tag/v3.3-rc1
the libffi-3.3.tar.gz published last Friday now ftbfs on powerpc-linux-gnu:
libtool: compile: powerpc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.
-I../include -Iinclude -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wall -fexceptions -MT src/powerpc/ffi.lo -MD -MP -MF
src/powerpc/.deps/ffi.Tpo -c ../src/powerpc/ffi.c -fPIC -DPIC -o
src/powerpc/.libs/ffi.o
In file included from ../src/powerpc/ffi.c:33:
../src/powerpc/ffi_powerpc.h:65:9: error: ‘__int128’ is not supported on this target
65 | typedef __int128 float128;
| ^~~~~~~~
make[3]: *** [Makefile:1274: src/powerpc/ffi.lo] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[2]: *** [Makefile:1348: all-recursive] Error 1
next prev parent reply other threads:[~2019-11-27 7:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:17 Anthony Green
2019-10-25 10:08 ` Matthias Klose
2019-10-25 10:29 ` John Paul Adrian Glaubitz
2019-10-25 14:41 ` Andreas Schwab
2019-10-25 14:44 ` John Paul Adrian Glaubitz
2019-10-25 18:32 ` Andreas Schwab
2019-10-25 18:37 ` John Paul Adrian Glaubitz
2019-10-25 19:04 ` Andreas Schwab
2019-10-25 19:07 ` John Paul Adrian Glaubitz
2019-10-26 11:35 ` Anthony Green
2019-10-26 12:54 ` Anthony Green
2019-10-31 19:49 ` Anthony Green
2019-10-31 20:32 ` John Paul Adrian Glaubitz
[not found] ` <CAAs=koj3HU08uxx36809NcPYe33xvEjUDsLwJc_9R8V4tbr9Zg@mail.gmail.com>
2019-10-31 22:16 ` John Paul Adrian Glaubitz
2019-11-01 8:01 ` John Paul Adrian Glaubitz
2019-11-01 22:24 ` John Paul Adrian Glaubitz
2019-11-08 9:21 ` Matthias Klose
2019-11-08 14:28 ` Anthony Green
2019-11-09 16:04 ` Matthias Klose
2019-11-09 17:46 ` Anthony Green
2019-11-10 16:22 ` Matthias Klose
2019-11-26 8:39 ` Matthias Klose
2019-11-26 23:25 ` Anthony Green
2019-11-27 7:54 ` Matthias Klose [this message]
2019-11-27 9:28 ` Anthony Green
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=816931f1-7ff7-60bf-82c1-e2221b1ec1dd@ubuntu.com \
--to=doko@ubuntu.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).