[Bug 252983] Error in Makefile for comms/hackrf-devel

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Jan 24 18:49:02 UTC 2021


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252983

            Bug ID: 252983
           Summary: Error in Makefile for comms/hackrf-devel
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: bob at vesterman.com

I just went to do a periodic update of my installed ports (using synth) and got
this error:

-------------------------
# synth status topLevelPackages.txt
Regenerating flavor index: this may take a while ...
Scanning entire ports tree.
 progress: 6.15%
culprit: comms/hackrf-devel
  Scan aborted because 'make' encounted an error in the Makefile.
  comms/hackrf-devel (return code = 1)
Flavor index generation failed: ports scan
--------------------------

I see hackrf-devel was just updated a few hours ago. I don't use hackrf-devel,
or hackrf, and have never even heard of them, so I guess synth scans absolutely
everything. So I guess this problem will prevent anyone who uses synth from
updating their ports, not just users of hackrf-devel.

I couldn't find any further detail on the error in synth's logs, but eventually
I found something on the web related to a similar problem for a different port,
which led to me running this command to find the cause:

--------------------------
# make -C /usr/ports/comms/hackrf-devel/ -V PORTNAME
make: "/usr/ports/comms/hackrf-devel//Makefile" line 26: Could not find
Makefile.git_rev
make: Fatal errors encountered -- cannot continue
make: stopped in /usr/ports/comms/hackrf-devel/
--------------------------

--- Comment #1 from Bugzilla Automation <bugzilla at FreeBSD.org> ---
Maintainer informed via mail

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list