net-misc/openssh does not support USE='${enabled_eol_flags%,}' anymore.
The Base system team *STRONGLY* recommends you not rely on this functionality,
since these USE flags required third-party patches that often trigger bugs
and are of questionable provenance.
If you must continue relying on this functionality, switch to
net-misc/openssh-contrib. You will have to remove net-misc/openssh from your
world file first: 'emerge --deselect net-misc/openssh'
In order to prevent loss of SSH remote login access, we will abort the build.
Whether you proceed with disabling the USE flags or switch to the -contrib
variant, when re-emerging you will have to set
  OPENSSH_EOL_USE_FLAGS_I_KNOW_WHAT_I_AM_DOING=yes
Sorry, but openssh no longer supports tcp-wrappers, and it seems like
you're trying to use it.  Update your ${EROOT}/etc/hosts.{allow,deny} please.
Running the full OpenSSH testsuite requires a usable shell for the 'portage'
user, so we will run a subset only.
After upgrading to openssh-8.2p1 please restart sshd, otherwise you
will not be able to establish new sessions. Restarting sshd over a ssh
connection is generally safe.
From openssh-9.2_p1-r1 the supplied systemd unit file defaults to
'Restart=on-failure', which causes the service to automatically restart if it
terminates with an unclean exit code or signal. This feature is useful for most users,
but it can increase the vulnerability of the system in the event of a future exploit.
If you have a web-facing setup or are concerned about security, it is recommended to
set 'Restart=no' in your sshd unit file.

net-misc/openssh does not support USE='${enabled_eol_flags%,}' anymore.
The Base system team *STRONGLY* recommends you not rely on this functionality,
since these USE flags required third-party patches that often trigger bugs
and are of questionable provenance.
If you must continue relying on this functionality, switch to
net-misc/openssh-contrib. You will have to remove net-misc/openssh from your
world file first: 'emerge --deselect net-misc/openssh'
In order to prevent loss of SSH remote login access, we will abort the build.
Whether you proceed with disabling the USE flags or switch to the -contrib
variant, when re-emerging you will have to set
  OPENSSH_EOL_USE_FLAGS_I_KNOW_WHAT_I_AM_DOING=yes
Sorry, but openssh no longer supports tcp-wrappers, and it seems like
you're trying to use it.  Update your ${EROOT}/etc/hosts.{allow,deny} please.
Running the full OpenSSH testsuite requires a usable shell for the 'portage'
user, so we will run a subset only.
After upgrading to openssh-8.2p1 please restart sshd, otherwise you
will not be able to establish new sessions. Restarting sshd over a ssh
connection is generally safe.
From openssh-9.2_p1-r1 the supplied systemd unit file defaults to
'Restart=on-failure', which causes the service to automatically restart if it
terminates with an unclean exit code or signal. This feature is useful for most users,
but it can increase the vulnerability of the system in the event of a future exploit.
If you have a web-facing setup or are concerned about security, it is recommended to
set 'Restart=no' in your sshd unit file.