Date: Wed, 17 Aug 2016 18:12:51 -0400 From: Diane Bruce <db@db.net> To: kargl@uw.edu Cc: Diane Bruce <db@db.net>, freebsd-ports@freebsd.org, freebsd-toolchain@freebsd.org Subject: Re: Problems with out libgcc_s.so in base Message-ID: <20160817221251.GA68398@night.db.net> In-Reply-To: <20160817211710.GA59205@troutmask.apl.washington.edu> References: <20160814230351.GA10587@troutmask.apl.washington.edu> <20160814233430.GA35872@night.db.net> <20160817211710.GA59205@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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:
> > > % cat ~/bin/gfc7
> > > #! /bin/sh
> > > DIR=`id -P sgk | sed 's/\:/\ /g' | awk '{print $9}'`
> > > export DIR
> > >
> > > LD_LIBRARY_PATH=$DIR/work/7/lib
> > > export LD_LIBRARY_PATH
> > >
> > > LD_RUN_PATH=$DIR/work/7/lib
> > > export LD_RUN_PATH
> > >
> > > $DIR/work/7/bin/gfortran -fno-backtrace $@
> >
> > 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.
>
> --
> Steve
>
Diane
--
- db@FreeBSD.org db@db.net http://www.db.net/~db
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160817221251.GA68398>