Bug 223174 - devel/riscv64-gcc: doesn't have libgcov.a; doesn't work with --coverage
Summary: devel/riscv64-gcc: doesn't have libgcov.a; doesn't work with --coverage
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Li-Wen Hsu
Depends on:
Reported: 2017-10-22 21:38 UTC by Enji Cooper
Modified: 2021-02-11 18:44 UTC (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Enji Cooper freebsd_committer 2017-10-22 21:38:03 UTC
In order for external toolchains to work with --coverage, libgcov.a needs to be present. This isn't the case for amd64 and riscv64.
Comment 1 commit-hook freebsd_committer 2017-10-22 21:40:48 UTC
A commit references this bug:

Author: ngie
Date: Sun Oct 22 21:39:58 UTC 2017
New revision: 324874
URL: https://svnweb.freebsd.org/changeset/base/324874

  Remove BROKEN_OPTIONS/MK_COVERAGE=no for gcc cross-toolchain reliant archs

  The cross-toolchain gcc toolchains aren't installing libgcov.a, but the host
  toolchain variants are. Don't hack around broken packages in the base system.

  PR:		223174

Comment 2 commit-hook freebsd_committer 2017-10-22 22:06:09 UTC
A commit references this bug:

Author: ngie
Date: Sun Oct 22 22:05:37 UTC 2017
New revision: 324875
URL: https://svnweb.freebsd.org/changeset/base/324875

  Disable MK_COVERAGE in Makefile.inc1 when working with broken gcc packages

  It makes more sense to do this in the top-level Makefile, instead of down in
  src.opts.mk .

  PR:	223174

Comment 3 Enji Cooper freebsd_committer 2017-11-05 20:10:10 UTC
lwhsu@ maintains devel/riscv64-gcc -- giving bug to him.
Comment 4 Mitchell Horne freebsd_committer 2021-01-12 00:04:41 UTC
Hi Enji,

Is this bug still relevant? If not, I'd like to close it. FWIW I don't see libgcov.a included as part of any of the amd64 gcc ports.

Comment 5 Mitchell Horne freebsd_committer 2021-02-11 18:44:39 UTC
This has lapsed. If the runtime-coverage work resumes, a new bug should be opened against devel/freebsd-gcc, which is the preferred GCC cross-toolchain these days.