Date: Thu, 05 Sep 2024 20:02:02 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 279692] '#include <csetjmp>' is broken: error: "If libc++ starts defining <setjmp.h>, the __has_include check should move to libc++'s <setjmp.h>" Message-ID: <bug-279692-29464-0I24oC4PqJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-279692-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-279692-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279692 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #7 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Bob Frazier from comment #5) QUOTE NOTE: in some cases, like a massive ports upgrade, using "make delete-old" might not be desirable until after many ports have already been re-built. END QUOTE Avoiding running "make delete-old" leads to the risk of silently finding and using out-of-date content in some of the upgrade's build activity. Such can make it harder to discover that there are problems to fix to be sure that the right content is used. "make delete-old-libs" is somewhat different for the criteria relative to keeping programs that do not yet have updated installs operational (still using old .so files and such). "make delete-old-libs" is appropriate after the upgrades to versions that use the newer .so libraries are in use instead. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279692-29464-0I24oC4PqJ>