From: "carlo.bramix@libero.it" <carlo.bramix@libero.it>
To: libffi-discuss@sourceware.org
Subject: Re: libffi 3.0.10rc4 available for testing
Date: Sun, 13 Feb 2011 11:03:00 -0000 [thread overview]
Message-ID: <24502344.1523421297594979073.JavaMail.defaultUser@defaultHost> (raw)
Hello,
I compiled and installed rc4 with mingw+msys without problems.
I'm using the stable GCC 3.4.5 rather than the GCC 4.x builds.
No testing on the functionalities has been done (I do not know how to do
it...).
Sincerely,
Carlo Bramini
>----Messaggio originale----
>Da: luislavena@gmail.com
>Data: 12/02/2011 17.11
>A: "Anthony Green"<green@redhat.com>
>Cc: <libffi-discuss@sourceware.org>
>Ogg: Re: libffi 3.0.10rc4 available for testing
>
>On Sat, Feb 12, 2011 at 11:45 AM, Anthony Green <green@redhat.com> wrote:
>>
>>
>> The iOS build is known to be broken and native windows / mingw is
>> completely untested, but I think we're in pretty good shape otherwise.
>> We just need more test results:
>>
>
>MinGW compilation succeed using rc3 and GCC 4.5.1 and 4.5.2. to run
>test it request expect and tcl which is not part of the toolkit I'm
>using, so will test with msysGit full installation (that contain these
>tools) and report back soon.
>
>Also cross compilation worked perfectly, except for the change of
>binaries location, but that is already known.
>--
>Luis Lavena
>AREA 17
>-
>Perfection in design is achieved not when there is nothing more to add,
>but rather when there is nothing more to take away.
>Antoine de Saint-Exupéry
>
next reply other threads:[~2011-02-13 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 11:03 carlo.bramix [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-12 14:44 Anthony Green
2011-02-12 16:12 ` Luis Lavena
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=24502344.1523421297594979073.JavaMail.defaultUser@defaultHost \
--to=carlo.bramix@libero.it \
--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).