[Bug 297564] sysutils/smartmontools: fix build after base 749318f2ae56

[email protected]
Newsgroups gmane.os.freebsd.devel.ports.bugs
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297564

            Bug ID: 297564
           Summary: sysutils/smartmontools: fix build after base
                    749318f2ae56
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
             Flags: maintainer-feedback?([email protected])
          Assignee: [email protected]

After base 749318f2ae56127abdffee405f8f4658efa1c807 ("libusb:
capsicumize libusb"), sysutils/smartmontools fails to build with errors
similar to:

  os_freebsd.cpp:2227:9: error: no matching function for call to
'libusb20_be_alloc_default'
   2227 |   pbe = libusb20_be_alloc_default();
        |         ^~~~~~~~~~~~~~~~~~~~~~~~~
  /usr/include/libusb20.h:299:26: note: candidate function not viable: requires
single argument 'pctx', but no arguments were provided
    299 | struct libusb20_backend *libusb20_be_alloc_default(struct
libusb20_be_ctx *pctx);
        |                          ^                        
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  1 error generated.

This is because base 749318f2ae56127abdffee405f8f4658efa1c807 changed
the prototype for libusb20_be_alloc_default() to add a "struct
libusb20_be_ctx *pctx" parameter. It looks like passing NULL is fine in
this case.

Since there was no separate __FreeBSD_version bump for this libusb
refactoring, use base f77fa28422ee455580d44498a4f36c6418e96dd0 ("video:
bump __FreeBSD_version for video(4) refactor") instead, which was
committed one day later.

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.