Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 30 Apr 2022 08:34:43 -0700
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Ed Maste <emaste@freebsd.org>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Profiled libraries on freebsd-current
Message-ID:  <Ym1XE9QSSvIy/4uo@troutmask.apl.washington.edu>
In-Reply-To: <CAPyFy2CuSFd7zm8BvrWYDv%2BEgM0Ryz-bxwWNzUEMEkm0fruokA@mail.gmail.com>
References:  <Ymt%2BICLaQPxx2knx@troutmask.apl.washington.edu> <CAPyFy2CuSFd7zm8BvrWYDv%2BEgM0Ryz-bxwWNzUEMEkm0fruokA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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.

-- 
Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Ym1XE9QSSvIy/4uo>