Stumbled on this while reading for the plist fragments.  Looking at
bsd.port.mk history this seems to be garbage collected almost an year
ago.

  revision 1.1579
  date: 2022/10/25 15:10:34;  author: naddy;  state: Exp;  lines: +1 -8;  
commitid
  : UOmr6kpMuQVhFRoj;
  bsd.port.mk: g/c the mips64 pkg_args handling
  
  Historically, bsd.lib.mk used to build lib*_pic.a libraries, except
  on mips64.  Ten years ago, bsd.lib.mk stopped creating lib*_pic.a
  files and the corresponding PFRAG.no_mips64 bits were removed from
  the ports tree.  Remove the _PKG_ARGS handling that was forgotten
  at the time.
  
  From Brad, ok sthen@

ok to drop the documentation as well?

diff /usr/src
commit - 723b5a505a05cabf3b61ec754f85f6b924dce47e
path + /usr/src
blob - 85925be829ac8932cc7c3eae47a090161a25e2a9
file + share/man/man5/bsd.port.mk.5
--- share/man/man5/bsd.port.mk.5
+++ share/man/man5/bsd.port.mk.5
@@ -2717,8 +2717,6 @@ see also
 Special arguments to pass to
 .Xr pkg_create 1 ,
 in addition to the default ones.
-For mips64 and pic libraries, see
-.Sx THE GENERATION OF PACKAGE INFORMATION .
 .It Ev PKG_CREATE
 User settings.
 Path to
@@ -4223,21 +4221,6 @@ or
 to
 .Ev PKG_ARGS .
 .Pp
-If libraries are built using
-.Pa bsd.lib.mk ,
-special care should be taken for mips64* architectures,
-which do not ever build
-.Pa *pic.a
-files (all mips code is pic already).
-.Nm
-automatically adds
-.Li "-Dno_mips64=1"
-or
-.Li "-Dno_mips64=0"
-to
-.Ev PKG_ARGS ,
-and the porter only needs to provide the appropriate fragment.
-.Pp
 .Xr pkg_add 1
 now calls
 .Xr ldconfig 8

Reply via email to