Problems with out libgcc_s.so in base

[Steve Kargl]

On Wed, Aug 17, 2016 at 06:12:51PM -0400, Diane Bruce wrote:
> On Wed, Aug 17, 2016 at 02:17:10PM -0700, Steve Kargl wrote:
> > On Sun, Aug 14, 2016 at 07:34:30PM -0400, Diane Bruce wrote:
> > > On Sun, Aug 14, 2016 at 04:03:51PM -0700, Steve Kargl wrote:
> > > > 
> > > > Freebsd-ports could also use a wrapper:
> > > 
> > > Yes. I have also suggested we use a wrapper to the ports guys.
> > > 
> > 
> > I thought about this a bit, and cleaner solution might be
> > to add the program suffix to libgcc_s.so.1.  For example,
> > 
> > % cat foo.f90
> > program foo
> >    print *, 'Hello'
> > end program
> > % gfortran6 -o z foo.f90 && ./z
> > /lib/libgcc_s.so.1: version GCC_4.6.0 required by \
> > /usr/local/lib/gcc6/libgfortran.so.3 not found
> > % ldconfig -r | grep libgcc
> >         6:-lgcc_s.1 => /lib/libgcc_s.so.1
> >         735:-lgcc_s.1 => /usr/local/lib/gcc6/libgcc_s.so.1
> > 
> > Clearly, ldd is looking for 735 but finds 6.  If the lang/gcc6 could
> > be convinced to build, install, and use libgcc_s6.so.1, then the
> > problem is solved without a wrapper.
> 
> I like this solution. 
> 

I have asked on gcc at gcc.gnu.org if it is possible to configure
gcc as above.  I know that one can bump the shared lib number,
but that won't solve the problem.

-- 
Steve