Bug 207065 - devel/llvm-devel: Fix scan-build
Summary: devel/llvm-devel: Fix scan-build
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Brooks Davis
Depends on:
Reported: 2016-02-09 18:41 UTC by Pedro F. Giffuni
Modified: 2016-09-02 22:14 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (brooks)

Fix ccc-analyzer (552 bytes, patch)
2016-02-09 18:41 UTC, Pedro F. Giffuni
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Pedro F. Giffuni freebsd_committer 2016-02-09 18:41:57 UTC
Created attachment 166812 [details]
Fix ccc-analyzer

Attempting to run scan-build in FreeBSD 10+ is likely to fail because it tries to find gcc which doesn't exist.
Changing the ccc-analyzer script to use cc/c++ instead works.

I have been experiencing this bug for more than a year in all llvm versions.
Comment 1 Pedro F. Giffuni freebsd_committer 2016-02-09 18:43:03 UTC
Comment on attachment 166812 [details]
Fix ccc-analyzer

(For some reason I haven't been able to attach patches from chromium lately)
Comment 2 Philippe Michel 2016-02-25 21:16:25 UTC
I'm interested to have this fixed as well, but I think it would be safer to use the compilers from the relevant port instead of cc/c++ : in -devel, use clang-devel, in, say 3.6 use clang36, etc...
Comment 3 commit-hook freebsd_committer 2016-03-05 12:35:46 UTC
A commit references this bug:

Author: brooks
Date: Sat Mar  5 12:35:29 UTC 2016
New revision: 410173
URL: https://svnweb.freebsd.org/changeset/ports/410173

  Update to 3.8.0 RC3.

  Update the version in the clang-format patch. [0]

  Attempt make ccc-analyzer have a usable default. [1]

  PR:		207065 [1]
  Submitted by:	kpneal@pobox.com [0]

Comment 4 Brooks Davis freebsd_committer 2016-03-05 12:39:01 UTC
(In reply to commit-hook from comment #3)

This commit includes a patch which is plausibly upstreamable.  Using the "current" version probably isn't something we can make work without patching and I'd rather having something that usually works than have to maintain a patch.  Please let me know if this improves the situation.  If so I'll get it pushed upstream and apply the patch where required.
Comment 5 Pedro F. Giffuni freebsd_committer 2016-03-05 14:38:23 UTC
For the record,
I opened Bug 26568 upstream with the patch.

I think it would be nice to have both options: upstream should use cc/c++ and we could have a post-build REINPLACE script to use the clang versions from the port.

It is, unfortunately, more work so I would be fine with just the upstreaming for now.
Comment 6 Brooks Davis freebsd_committer 2016-09-02 22:14:57 UTC
What we have works well enough for now so close this.