Skip to content

Conversation

@auerswal
Copy link
Collaborator

@auerswal auerswal commented Jan 7, 2026

Improve portability to NetBSD by adapting two patches from the NetBSD package https://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/net/fping/. This addresses GH issue #450.

Testing string equality using "test" is done with the "="
operator.  Bash also accepts "==", but this is not portable.
The issue was noticed on NetBSD, which uses a patch to the
generated "configure" script[1].

[1] https://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/net/fping/patches/patch-configure?rev=1.3;content-type=text%2Fplain
NetBSD does not know the IP_RECVTOS socket option.  Thus
conditionally compile setting this option only when it is
defined.

This is the same change as used in the NetBSD package[1],
with thanks to "adam".

[1] https://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/net/fping/patches/patch-src_fping.c?rev=1.5;content-type=text%2Fplain
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @auerswal, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the fping utility's compatibility with the NetBSD operating system. It incorporates two key patches derived from the NetBSD package source, specifically addressing GitHub issue #450. The changes ensure more robust behavior on NetBSD by adjusting build configuration and conditionally compiling platform-specific socket options, leading to better overall portability.

Highlights

  • NetBSD Compatibility: Enhanced compatibility with NetBSD by integrating specific patches, directly addressing GitHub issue IP_RECVTOS is not available on NetBSD #450.
  • Build Configuration Fix: Corrected a shell comparison operator in configure.ac to improve IPv6 detection logic.
  • Conditional Compilation: Improved portability in src/fping.c by conditionally compiling IP_RECVTOS socket option usage based on its definition.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request improves NetBSD compatibility by applying two targeted patches. The change in configure.ac to use = instead of == for string comparison in a test command enhances shell script portability. The modification in src/fping.c correctly wraps the usage of the IP_RECVTOS socket option within an #if defined(IP_RECVTOS) block, as this option is not available on NetBSD. These changes are well-implemented and directly address the compatibility issue. The code is clean and I have no suggestions for improvement.

@coveralls
Copy link

Coverage Status

coverage: 88.037%. remained the same
when pulling 85e842f on auerswal:netbsd-compat
into 7dcd667 on schweikert:develop.

@gsnw-sebast gsnw-sebast linked an issue Jan 7, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

IP_RECVTOS is not available on NetBSD

3 participants