Re: Upgrading libffi

2020-01-12 Thread Miro HronĨok
On 12. 01. 20 13:38, Anthony Green wrote: * I can't get any python to mockbuild, even without the new libffi. There's an error in the %install process. Known problem? What does "any python" mean? python26, python27, python3, python39, python37, python36, python35, python34, pypy, pypy3 al

Re: Upgrading libffi

2020-01-12 Thread Kevin Fenzi
On Sun, Jan 12, 2020 at 07:38:01AM -0500, Anthony Green wrote: > Kevin Fenzi writes: > > Sounds good to me. If you run into any issues let me know. > > I've run three kinds of problems so far... > > * programs that link against both libffi and other libraries that link > to libffi (eg. glib2,

Re: Upgrading libffi

2020-01-12 Thread Anthony Green
Kevin Fenzi writes: > Sounds good to me. If you run into any issues let me know. I've run three kinds of problems so far... * programs that link against both libffi and other libraries that link to libffi (eg. glib2, gobject-introspection). We need to push new versions of these libraries a

Re: Upgrading libffi

2020-01-10 Thread Kevin Fenzi
On Fri, Jan 10, 2020 at 06:24:35AM -0500, Anthony Green wrote: > > Anthony Green writes: > > Kevin Fenzi writes: > >> I suppose you could also > >> add both old and new libffi source to the libffi package and build them > >> both (old to compat), rebuild in side tag and drop the old > >> sources

Re: Upgrading libffi

2020-01-10 Thread Anthony Green
Anthony Green writes: > Kevin Fenzi writes: >> I suppose you could also >> add both old and new libffi source to the libffi package and build them >> both (old to compat), rebuild in side tag and drop the old >> sources/compat. >> Does that make sense? > > I like this idea because it seems simp

Re: Upgrading libffi

2020-01-08 Thread Anthony Green
Kevin Fenzi writes: > I suppose you could also > add both old and new libffi source to the libffi package and build them > both (old to compat), rebuild in side tag and drop the old > sources/compat. > > Does that make sense? I like this idea because it seems simple. Thanks for the tip! AG --

Re: Upgrading libffi

2020-01-08 Thread Anthony Green
"Colin Walters" writes: > Anthony, I think all of the work you've done on libffi has been very valuable > to the FOSS community. It's good code that has gained widespread use in > critical projects such as glib, python, etc. Thanks Colin! > Which commit to libffi for aarch64 porting required

Re: Upgrading libffi

2020-01-08 Thread Colin Walters
Hi, On Mon, Jan 6, 2020, at 6:11 PM, Anthony Green wrote: > > I released a new version of libffi a month or so ago, the first one in 5 > years. There's an ABI change that was unavoidable in order to > accommodate the aarch64 port, and the sonumber was bumped. Anthony, I think all of the work yo

Re: Upgrading libffi

2020-01-08 Thread Igor Gnatenko
If you push changes to the dist-git, I can handle builds and rebuilds. On Wed, Jan 8, 2020, 19:58 Kevin Fenzi wrote: > On Tue, Jan 07, 2020 at 10:20:59AM -0500, Anthony Green wrote: > > Neal Gompa writes: > > > > > RPM does not use libffi at all. > > > > My bad.. rpmbuild, through it's use of g

Re: Upgrading libffi

2020-01-08 Thread Kevin Fenzi
On Tue, Jan 07, 2020 at 10:20:59AM -0500, Anthony Green wrote: > Neal Gompa writes: > > > RPM does not use libffi at all. > > My bad.. rpmbuild, through it's use of gdb, which requires python, which > requires libffi. So my naive use of mock to try to build a new version > of libffi and all of

Re: Upgrading libffi

2020-01-07 Thread Anthony Green
Neal Gompa writes: > RPM does not use libffi at all. My bad.. rpmbuild, through it's use of gdb, which requires python, which requires libffi. So my naive use of mock to try to build a new version of libffi and all of it's dependencies fail. > That said, it's quite easy to do a > rebuild of li

Re: Upgrading libffi

2020-01-06 Thread Neal Gompa
On Mon, Jan 6, 2020 at 11:02 PM Anthony Green wrote: > > Guido Aulisi writes: > > If you know all depending packages will get updated in an acceptable > > time to the new ABI, you can wait for this to happen, and then rebuild > > all in rawhide. > > The API is mostly the same. Virtually everythi

Re: Upgrading libffi

2020-01-06 Thread Anthony Green
Guido Aulisi writes: > If you know all depending packages will get updated in an acceptable > time to the new ABI, you can wait for this to happen, and then rebuild > all in rawhide. The API is mostly the same. Virtually everything should already build with the new version (Debian has tested thi

Re: Upgrading libffi

2020-01-06 Thread Guido Aulisi
Il giorno lun, 06/01/2020 alle 18.11 -0500, Anthony Green ha scritto: > I released a new version of libffi a month or so ago, the first one > in 5 > years. There's an ABI change that was unavoidable in order to > accommodate the aarch64 port, and the sonumber was bumped. > > I am also the Fedora

Upgrading libffi

2020-01-06 Thread Anthony Green
I released a new version of libffi a month or so ago, the first one in 5 years. There's an ABI change that was unavoidable in order to accommodate the aarch64 port, and the sonumber was bumped. I am also the Fedora package maintainer for libffi, but admit that I don't have the time or expertise