On Mon, Sep 08, 2014 at 09:01:52PM +0200, Henrik Friedrichsen wrote: > > On 09/08/2014 08:32 PM, Stuart Henderson wrote: > >In general: anything which configure scripts might pick up should > >either be listed as a dependency, or explicitly disabled. > This port does not use autoconf. The error message mentioned is printed by > the script which detects whether libexecinfo is present in order to turn > on/off a preprocessor switch which disables the relevant code. Is this still > problematic?
Yes, it's problematic because we need predictable builds that dont depend on the random presence of some dependencies - thus, either we need to say we depend on libexecinfo and mark LIB_DEPENDS as such, or explicitely disable it to ensure it's not picked up if randomly found at build time depending on the environment on the builder. Landry
