Date: Fri, 29 Apr 2022 23:13:36 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Profiled libraries on freebsd-current Message-ID: <YmzTkIdpR0bpYHvu@troutmask.apl.washington.edu> In-Reply-To: <54761641-8AD3-44A6-8620-F1341ED9AB56@yahoo.com> References: <B1FD9D1B-EE31-4114-8F05-E249283A2408@yahoo.com> <CDB73C3B-B56C-4C17-857D-EB56BEC3E323@yahoo.com> <YmxGyaP40bR6jq8v@troutmask.apl.washington.edu> <54761641-8AD3-44A6-8620-F1341ED9AB56@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 29, 2022 at 02:54:17PM -0700, Mark Millard wrote: > On 2022-Apr-29, at 13:12, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > > > The evenual absence of libc_p.a and libm_p.a will break GCC's > > -pg option in GCC. One will then need to know how to change the > > GCC source or install symlinks for to point *_p.a a the *.a libs. > > > > src/tree/tools/build/mk/OptionalObsoleteFiles.inc shows the > following that does include those 2 files as ones considered > obsolete (i.e., to be removed) by WITHOUT_PROFILE: > (snip) > > I expect that this is part of the mechanism that will > ultimately remove those then-out-of-date files from > systems when WITH_PROFILE is no longer supported. > > Metion was made of "[a] similar change is still needed > for GCC" --but I've no clue of the details or status. > Therein lies the problem. None of the people pushing the removal of WITH[OUT]_PROFILE have submitted a patch to fix GCC. Anyone installing a lang/gccXXX port will be met with errors when using -pg. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YmzTkIdpR0bpYHvu>