[MacPorts] #74166: libetonyek @0.1.2: configure: error: Required boost headers not found. (was: libetonyek: configure failed)

[MacPorts]

#74166: libetonyek @0.1.2: configure: error: Required boost headers not found.
-------------------------+----------------------
  Reporter:  benlisp     |      Owner:  RJVB
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.12.5
Resolution:              |   Keywords:
      Port:  libetonyek  |
-------------------------+----------------------

Comment (by ryandesign):

 Replying to [comment:8 RJVB]:
 > > erroneously attached to a wiki page
 >
 > How, what, where???

 Sometimes people inadvertently attach files to wiki pages instead of
 tickets. I guess that happened to benlisp in this case and Clemens noticed
 it and moved the files here where they belong.

 > The only thing I can see is that the boost headers aren't found on your
 system, but I suspect there's a problem on end,  given how the build
 succeeded for a user who clearly wasn't used to "hacking around".
 >
 > AFAICT the boost header location is injected correctly into CPPFLAGS
 exactly as it happens on my end, so I have no idea what's going on here.

 The config.log shows that although the boost header was found, it could
 not be used due to this error:

 {{{
 /opt/local/libexec/boost/1.76/include/boost/unordered/detail/fwd.hpp:53:16:
 error: no member named 'piecewise_construct' in namespace 'std'; did you
 mean 'piecewise_construct_t'?
    53 |     using std::piecewise_construct;
       |           ~~~~~^~~~~~~~~~~~~~~~~~~
       |                piecewise_construct_t
 /Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk/usr/include/c++/v1/__utility/piecewise_construct.h:20:29:
 note: 'piecewise_construct_t' declared here
    20 | struct _LIBCPP_TEMPLATE_VIS piecewise_construct_t { explicit
 piecewise_construct_t() = default; };
       |                             ^
 }}}

 That was a build of 0.1.2. Since your updated 0.1.13 Portfile builds
 successfully, it doesn't merit further investigation.

 Replying to [comment:7 RJVB]:
 > The powers that be are welcome to feel free to polish the attached
 Portfile following the latest fashion and commit it O:^)

 You, as the maintainer of the port, are welcome to submit a pull request
 whenever you wish to update one of your ports, especially since you have
 not marked the port "openmaintainer", thus indicating that you wish to
 retain more control of updating this port and do not wish others to do so.

-- 
Ticket URL: <https://trac.macports.org/ticket/74166#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS