Re: help with understanding __BSD_VISIBLE

2019-07-21 Thread Theo de Raadt
>Philip Guenther writes: > >> There are four options here: >> 1) change the software to not use the name 'bcrypt' for a non-static >> function. OpenBSD has only been using it for 15 years... > >Agree, but for now I'm trying to keep changes to a minimum as I work out >larger issues. This is in an

Re: help with understanding __BSD_VISIBLE

2019-07-15 Thread Allan Streib
Philip Guenther writes: > There are four options here: > 1) change the software to not use the name 'bcrypt' for a non-static > function. OpenBSD has only been using it for 15 years... Agree, but for now I'm trying to keep changes to a minimum as I work out larger issues. This is in an erlang w

Re: help with understanding __BSD_VISIBLE

2019-07-13 Thread Philip Guenther
On Fri, Jul 12, 2019 at 10:39 AM Allan Streib wrote: > Probably an elementary question stemming from my lack of C expertise. > > I am trying to complile some C code that includes its own "bcrypt" > function. This is conflicting with the declaration in pwd.h. > > error: conflicting types for '

Re: help with understanding __BSD_VISIBLE

2019-07-12 Thread Otto Moerbeek
On Fri, Jul 12, 2019 at 03:35:54PM -0400, Allan Streib wrote: > Probably an elementary question stemming from my lack of C expertise. > > I am trying to complile some C code that includes its own "bcrypt" > function. This is conflicting with the declaration in pwd.h. > > error: conflicting t