Rebuild 1.78 with newer compilers

[jakirkham]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[jakirkham]

@conda-forge-admin, please re-render

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/boost-cpp-feedstock/actions/runs/3363884336.

[isuruf]

If there is indeed an ABI breakage, then rebuilding will break older packages. So we should not merge it and investigate more.

[varlackc]

There seem to be some conflicts in the current branch.

Also, it might be a good idea to modify the home url to use https instead of http

In addition, we might want to add a dev_url and doc_url

[h-vetinari]

We now have 1.82 and will migrate to that soon. All other changes need to happen on https://github.com/conda-forge/boost-feedstock now.