Macos: Search for C++ and Obj C compilers

[andrewc12]

Motivation and Context

The macos port requires additional compilers so I'm splitting the changes out to see if they break anything in non macos builds

Description

Search for C++ and Obj C compilers in configure script

How Has This Been Tested?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Breaking change (fix or feature that would cause existing functionality to change)
• Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the OpenZFS code style requirements.
• I have updated the documentation accordingly.
• I have read the contributing document.
• I have added tests to cover my changes.
• I have run the ZFS Test Suite with this change applied.
• All commit messages are properly formatted and contain Signed-off-by.

[andrewc12]

Has anyone had a chance to look at this yet?

[behlendorf]

No objection, but we'll want to annotate all of these macos commits so they're easy to find. We've often done that for Linux and FreeBSD by prepending "Linux: " or "FreeBSD" to the commit message subject.

[andrewc12]

No objection, but we'll want to annotate all of these macos commits so they're easy to find. We've often done that for Linux and FreeBSD by prepending "Linux: " or "FreeBSD" to the commit message subject.

Done

[behlendorf]

Thanks. I'm good with starting to bring in these macos changes. Let's just make sure all of of these commits have the "Macos:" prefix so they're easy to identify. Since some of these infrastructure may not be used yet that'll help make it clear why a change was made.