Re: Incompatible change in libgc with no soname bump

2014-05-17 Thread Rex Dieter
Rex Dieter wrote: > Jerry James wrote: > >> %{_libdir}/libgc.so.1.0.3 exists in both F-20 and Rawhide, and both >> have an soname of libgc.so.1, but the two libraries are NOT >> compatible. I just discovered this by accident while trying to >> rebuild ecl for a totally different reason. It fail

Re: Incompatible change in libgc with no soname bump

2014-05-17 Thread Rex Dieter
Jerry James wrote: > %{_libdir}/libgc.so.1.0.3 exists in both F-20 and Rawhide, and both > have an soname of libgc.so.1, but the two libraries are NOT > compatible. I just discovered this by accident while trying to > rebuild ecl for a totally different reason. It fails like so: > > libeclmin.a

Re: Incompatible change in libgc with no soname bump

2014-05-15 Thread Rex Dieter
On 05/15/2014 10:44 AM, Jerry James wrote: %{_libdir}/libgc.so.1.0.3 exists in both F-20 and Rawhide, and both have an soname of libgc.so.1, but the two libraries are NOT compatible. I just discovered this by accident while trying to rebuild ecl for a totally different reason. It fails like so:

Incompatible change in libgc with no soname bump

2014-05-15 Thread Jerry James
%{_libdir}/libgc.so.1.0.3 exists in both F-20 and Rawhide, and both have an soname of libgc.so.1, but the two libraries are NOT compatible. I just discovered this by accident while trying to rebuild ecl for a totally different reason. It fails like so: libeclmin.a(alloc_2.o): In function `init_a