[Bug 260523] ar: with -T option disabled
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 260523] [exp-run] ar with -T option disabled"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 20 Jan 2022 00:25:41 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260523
Kubilay Kocak <koobs@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[exp-run] ar with -T option |ar: with -T option disabled
|disabled |
Flags| |maintainer-feedback?(emaste
| |@freebsd.org)
See Also| |https://github.com/llvm/llv
| |m-project/issues/25899
CC|ports-bugs@FreeBSD.org |emaste@freebsd.org,
| |portmgr@FreeBSD.org
Product|Ports & Packages |Base System
URL| |https://reviews.freebsd.org
| |/D33553
Status|New |In Progress
Component|Ports Framework |bin
Assignee|portmgr@FreeBSD.org |emaste@freebsd.org
Version|Latest |CURRENT
Depends on| |260810
--- Comment #11 from Kubilay Kocak <koobs@FreeBSD.org> ---
^Triage: No longer an exp-run (please just just the flag). Assign to committer
resolving, re-classify (base issue, affecting ports, with base change)
Given comment 10:
"The warning will be changed to an error in the future (in main), once ports no
longer use -T." .. leave issues blocking this (in progress) issue, at least
for tracking purposes.
@Ed Is there any value/desire here to change our ar over time / long-term to be
consistent with other ar's, or is that effective a noop given the switch to
llvm-ar? Said another way, is the target state that 'our ar' is deprecated and
removed?
Referenced Bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260810
[Bug 260810] www/node*: incorrect ar invocation
--
You are receiving this mail because:
You are on the CC list for the bug.