-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
El Thu, 17 Jan 2013 06:35:08 -0500 (EST)
Anthony Green escribió:
> Dennis wrote:
> > I am right now building a compat-libffi package that has just the
> > old .so nothing to be built against. so expect that early this week
> > the .so of libffi will b
Dennis wrote:
> I am right now building a compat-libffi package that has just the
> old .so nothing to be built against. so expect that early this week
> the .so of libffi will be bumped.
Hey, thanks Dennis! I really appreciate this.
I'm hoping to release 3.0.12 soon and get that into the F19 re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
El Fri, 02 Nov 2012 16:04:29 -0400
Adam Jackson escribió:
> On 11/2/12 3:18 PM, Anthony Green wrote:
> > Several months ago I attempted to upgrade libffi 3.0.10 to 3.0.11.
> > The change was reverted because the soname change in this version of
> > th
On Fri, Nov 02, 2012 at 03:23:48PM -0700, Toshio Kuratomi wrote:
> And has been since August. Development starts when rawhide and F-next
> branch.
We need some way to put this in bigger letters.
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁
--
devel mailing list
devel@lists.fedoraproj
On Fri, Nov 02, 2012 at 04:49:01PM -0400, Bill Nottingham wrote:
> Colin Walters (walt...@verbum.org) said:
> > On Fri, 2012-11-02 at 16:04 -0400, Adam Jackson wrote:
> >
> > > It looks like libffi is emitted into the minimal buildroot (rpm-build ->
> > > pkg-config -> glib2 -> libffi), so durin
Colin Walters (walt...@verbum.org) said:
> On Fri, 2012-11-02 at 16:04 -0400, Adam Jackson wrote:
>
> > It looks like libffi is emitted into the minimal buildroot (rpm-build ->
> > pkg-config -> glib2 -> libffi), so during the transition we'll need to
> > build both sonames of libffi. It might
On Fri, 2012-11-02 at 16:04 -0400, Adam Jackson wrote:
> It looks like libffi is emitted into the minimal buildroot (rpm-build ->
> pkg-config -> glib2 -> libffi), so during the transition we'll need to
> build both sonames of libffi. It might be worth keeping a compat-libffi
> around for a re
On 11/2/12 3:18 PM, Anthony Green wrote:
Several months ago I attempted to upgrade libffi 3.0.10 to 3.0.11.
The change was reverted because the soname change in this version of
the library broke the build environment. I would still like to get
3.0.11 in Fedora. I don't anticipate any future ABI
Several months ago I attempted to upgrade libffi 3.0.10 to 3.0.11. The change
was reverted because the soname change in this version of the library broke the
build environment. I would still like to get 3.0.11 in Fedora. I don't
anticipate any future ABI-breaking changes, and 3.0.12 will incl
