Re: Runtime loader issue

2018-05-10 Thread Steve Kargl
On Wed, May 09, 2018 at 04:45:51PM -0700, Steve Kargl wrote: > In review PR 228007, it came to my attention some individuals are > mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD > issue". See It seems we've had the same discussion 2 years ago. My time flies. ttps://lists.freeb

Re: Runtime loader issue

2018-05-10 Thread Wojciech Puchar
.so.2. This, however, introduces an incompatibility with what is actually distributed by GCC. Finally, can people stop referring to the above error as "gfortran's FreeBSD issue". This is a FreeBSD runtime loader issue. Our libgcc also lacks some functionality compared to t

Re: Runtime loader issue

2018-05-10 Thread Steve Kargl
On Thu, May 10, 2018 at 06:21:51PM +0200, Tijl Coosemans wrote: > On Wed, 9 May 2018 16:45:51 -0700 Steve Kargl > wrote: > > > > So, the runtime loader finds 6 instead of 716, tries to link, > > fails, and issues an error message. There are a number ways to > > fix this issue. > > > > 1) By f

Re: Runtime loader issue

2018-05-10 Thread Diane Bruce
On Thu, May 10, 2018 at 08:15:22AM -0700, Steve Kargl wrote: > On Thu, May 10, 2018 at 10:24:52AM -0400, Diane Bruce wrote: > > On Thu, May 10, 2018 at 10:46:31AM +0300, Gleb Popov wrote: > > > On Thu, May 10, 2018 at 2:45 AM, Steve Kargl < > > > s...@troutmask.apl.washington.edu> wrote: > > > ...

Re: Runtime loader issue

2018-05-10 Thread Tijl Coosemans
th.so.0 => /usr/local/lib/gcc7/libquadmath.so.0 (0x200bb7000) >libc.so.7 => /lib/libc.so.7 (0x200df7000) > >This works for this particular name conflict. Hopefully, FreeBSD >never needs to bump /lib/libgcc_s.so.1 to /lib/libgcc_s.so.2. This, >however, introdu

Re: Runtime loader issue

2018-05-10 Thread Steve Kargl
On Thu, May 10, 2018 at 10:24:52AM -0400, Diane Bruce wrote: > On Thu, May 10, 2018 at 10:46:31AM +0300, Gleb Popov wrote: > > On Thu, May 10, 2018 at 2:45 AM, Steve Kargl < > > s...@troutmask.apl.washington.edu> wrote: > > > > > In review PR 228007, it came to my attention some individuals are >

Re: Runtime loader issue

2018-05-10 Thread Diane Bruce
nd entry 716, and load the correct libgcc_s.so.1. This breaks if the bad libgcc is already linked. We'd have to rip out the original bindings at run time, then re-bind to a new libgcc. I looked at the rtld code months ago. Nasty and silly. > > > >Admittedly, I haven't

Re: Runtime loader issue

2018-05-10 Thread Gleb Popov
ibquadmath.so.0 => /usr/local/lib/gcc7/libquadmath.so.0 (0x200bb7000) > libc.so.7 => /lib/libc.so.7 (0x200df7000) > >This works for this particular name conflict. Hopefully, FreeBSD >never needs to bump /lib/libgcc_s.so.1 to /lib/libgcc_s.so.2. This, >however

Runtime loader issue

2018-05-09 Thread Steve Kargl
r, introduces an incompatibility with what is actually distributed by GCC. Finally, can people stop referring to the above error as "gfortran's FreeBSD issue". This is a FreeBSD runtime loader issue. -- Steve ___ freebsd-ports@freeb