Date: Sun, 26 May 2019 08:39:16 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Diane Bruce <db@db.net> Cc: Konstantin Belousov <kostikbel@gmail.com>, Yuri <yuri@rawbw.com>, Freebsd hackers list <freebsd-hackers@freebsd.org> Subject: Re: What is the portable 128-bit floating point type? Message-ID: <20190526153916.GA60618@troutmask.apl.washington.edu> In-Reply-To: <20190526115851.GA65430@night.db.net> References: <eb15d9e4-c1d4-3886-a3b7-1264c12396cd@rawbw.com> <20190525200437.GV2748@kib.kiev.ua> <e13bc70d-4d7e-3407-a0a0-14a64f94addd@rawbw.com> <20190525210311.GW2748@kib.kiev.ua> <20190525231310.GB56490@troutmask.apl.washington.edu> <20190526115851.GA65430@night.db.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 26, 2019 at 07:58:51AM -0400, Diane Bruce wrote: > On Sat, May 25, 2019 at 04:13:10PM -0700, Steve Kargl wrote: > > On Sun, May 26, 2019 at 12:03:11AM +0300, Konstantin Belousov wrote: > > > On Sat, May 25, 2019 at 01:50:24PM -0700, Yuri wrote: > > > > On 2019-05-25 13:04, Konstantin Belousov wrote: > ... > > > On the other hand, I have no idea if any support is required from > > > libgcc (probably it is), and we almost certainly do not have it in > > > the base library. > > > > This is part of the problem with gfortran finding the wrong > > libgcc_s.so. > > Regarding this see https://reviews.freebsd.org/D11482#423561 > and https://wiki.freebsd.org/libgcc%20problem > I was aware of the latter wiki page. The former is interesting. I wasn't aware of the former. Nice to see someone(s) taking an interest in the missing libgcc_s.so symbols. Seems that my efforts [1] to track the symbols missing for gfortran may have paiid off. [1] https://lists.freebsd.org/pipermail/freebsd-ports/2019-February/115593.html -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190526153916.GA60618>