Date: Sat, 30 Apr 2022 16:07:48 -0400 From: Ed Maste <emaste@freebsd.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Profiled libraries on freebsd-current Message-ID: <CAPyFy2AcKcT3NmpA5cs0WG4B7gPCJwdax%2BPp02YHEQBmJ10ZtQ@mail.gmail.com> In-Reply-To: <Ym1XE9QSSvIy/4uo@troutmask.apl.washington.edu> References: <Ymt%2BICLaQPxx2knx@troutmask.apl.washington.edu> <CAPyFy2CuSFd7zm8BvrWYDv%2BEgM0Ryz-bxwWNzUEMEkm0fruokA@mail.gmail.com> <Ym1XE9QSSvIy/4uo@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 30 Apr 2022 at 11:34, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > > On Sat, Apr 30, 2022 at 09:39:32AM -0400, Ed Maste wrote: > > On Fri, 29 Apr 2022 at 01:58, Steve Kargl > > <sgk@troutmask.apl.washington.edu> wrote: > > > > > > If one looks at src.conf(5), one finds > > > > > > WITH_PROFILE > > > Build profiled libraries for use with gprof(8). This option is > > > deprecated and is not present in FreeBSD 14. > > > > > > I assume that the *_p.a libraries will no longer be built and > > > installed on FreeBSD 14 and later. Is this correct? > > > > FreeBSD 14 is not yet released, of course, but that is indeed the > > intent. PR256874 reports that a GCC patch (to stop linking against > > _p.a) is in the works but unfortunately has not had an update for some > > time. > > I see. It only took me 2+ years to get > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89125 > > committed to the GCC repository. Good luck with > getting your patch upstream. Heh, thanks. I have just now changed the WITH_PROFILE description to state "a future version of FreeBSD" since it may well not happen for FreeBSD 14. We could also just install libc_p.a as a symlink to libc.a (and same for the other _p.a archives).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2AcKcT3NmpA5cs0WG4B7gPCJwdax%2BPp02YHEQBmJ10ZtQ>