On Thu, Mar 10, 2016 at 3:03 PM, Matthias Klose <d...@ubuntu.com> wrote: > On 07.03.2016 12:59, Richard Henderson wrote: >> >> On 03/06/2016 07:24 PM, Matthias Klose wrote: >>> >>> On 05.03.2016 19:28, Richard Henderson wrote: >>>> >>>> When I went to apply my symbol versioning patch to upstream, >>>> I discovered that upstream had already bumped their soname to >>>> 6.4.0, beyond the bump that I'd applied to gcc to 5.0.0. >>>> >>>> So I bumped upstream to 7.0.0, including the symbol versioning, >>>> and this adjusts gcc to match. >>> >>> >>> Looking at the libffi upstream git repo, I can't find this change >>> upstream, and >>> neither mentioned on the libffi mailing list. What am I missing? >> >> >> That must of libffi's workflow is via github, I think. >> >> https://github.com/atgreen/libffi/pull/230 > > > well, then I don't understand the subject, because there's no upstream > commit yet. Plus this patch doesn't seem to be relevant for GCC because > libffi is only used as a convenience library, and isn't installed at all. > Unless a distributor decides to ship libffi built from the GCC sources > again.
Which I incidentially (as the original bugreporter) do. The shared libffi is always built when bootstrapping. It's not installed by a toplevel make install but a make install inside $target/libffi/ works just fine. Richard. > Matthias >
