Issues with config.h

Joshua Root jmr at macports.org
Thu Aug 4 14:21:13 UTC 2022


On 2022-8-4 23:36 , Robert Kennedy wrote:
> I am working on creating a new port that uses its own *config.h*.  See 
> attached.  The project compiles and builds just in clang outside of 
> Macports but when it is built via Macports, a number of macro redefined 
> warnings are generated:
> 
> e.g.
> 
>     .*/config.h:29:9: warning: 'HAVE_STDINT_H' macro redefined*
>     *#define HAVE_STDINT_H*
>     *        ^*
>     *./config.h:42:9: note: previous definition is here*
>     *#define HAVE_STDINT_H 1*
> 
> 
> I suspect Macports or the compiler is creating or referencing another 
> *config.h*.

Unlikely, but it's very difficult for anyone else to know what's 
happening unless you share your Portfile. For your own investigation, 
the -H compiler option may be useful.

- Josh


More information about the macports-dev mailing list