[MacPorts] #62618: dav1d @0.8.2: build fails on leopard PPC (at least) with several errors

[MacPorts]

#62618: dav1d @0.8.2: build fails on leopard PPC (at least) with several errors
---------------------+---------------------------
  Reporter:  kencu   |      Owner:  ctreleaven
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:
Resolution:          |   Keywords:  leopard tiger
      Port:  dav1d   |
---------------------+---------------------------

Comment (by ballapete):

 Could be the problem is much simple – stdlib.h on PPC Leopard has:

 {{{
   253   #if !defined(_ANSI_SOURCE) && (!defined(_POSIX_C_SOURCE) ||
 defined(_DARWIN_C_SOURCE))
   254   #include <machine/types.h>
   255
   256   #ifndef _DEV_T
   257   typedef __darwin_dev_t  dev_t;
   258   #define _DEV_T
   259   #endif
   260
   261   #ifndef _MODE_T
   262   typedef __darwin_mode_t mode_t;
   263   #define _MODE_T
   264   #endif
   265
   266   u_int32_t
   267            arc4random(void);
 }}}

 `<machine/types.h>` then includes the proper C header file, either
 `/usr/include/ppc/types.h` or `/usr/include/i386/types.h`. Could be the
 guard prevents `<machine/types.h>` from being included… I'll find that in
 a few hours because right now `port` is trying to upgrade some trivial
 ports like `sqlite3` or `python37`…

 I am trying to solve such problems with C header files by letting `port`
 try to build the port and fail. Then I have in *compilation* buffer the
 compiler invocation. By changing to the proper working directory I can try
 to establish the same environment settings and invoke the compiler with a
 small change. By adding `-dD` and `-E` to the C compiler switches I can
 see in the pre-processed output file why an inclusion happened or not.
 Whether the C header was included can be found by adding `-H` to the C
 compiler switches.

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