Would it make sense to give Ansible 2.2.1.0 a try first? I'd like to avoid
backporting to Ansible if we can avoid it.

-D...


On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <[email protected]> wrote:

> Hmm, that's disconcerting.  I certainly don't mind documenting the
> workaround that you've proposed in METRON-708
>
> On Thu, Feb 9, 2017 at 1:05 PM, [email protected] <[email protected]> wrote:
>
> > Has anybody attempted to set up ansible 2.0.0.2 recently on a fresh mac
> > using brew and the steps we outline here
> > <https://github.com/apache/incubator-metron/tree/master/
> > metron-deployment/vagrant/full-dev-platform#os-x>?
> > I received a new laptop this week, so I ran through some of our setup
> > documentation to test any assumptions that may exist in our READMEs (see
> > METRON-708 <https://github.com/apache/incubator-metron/pull/447> for
> some
> > of my updates) before restoring my TM backup.
> >
> > It looks like the installation process broke because of some function
> > renaming <https://github.com/openssl/openssl/issues/1190> within
> > openssl.  I'd
> > like to get some secondary validation of this issue if anybody else has
> an
> > environment where they can give it a shot.  I think I was able to resolve
> > the issue by back-porting this commit
> > <https://github.com/Homebrew/homebrew-core/commit/
> > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > I just haven't had time to complete more comprehensive testing (i.e.
> > spinning up quick-dev or full-dev).  Once we agree on the resolution to
> > this I can update METRON-708 appropriately.
> >
> >
> > Here are some relevant logs taken from
> > ~/Library/Logs/Homebrew/ansible/09.python:
> >
> > building '_openssl' extension
> >
> > creating build/temp.macosx-10.12-intel-2.7/build
> >
> > creating build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > intel-2.7
> >
> > clang -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386
> -g
> > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -DENABLE_DTRACE
> -DMACOSX
> > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -fwrapv
> > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386
> -pipe
> > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > include/python2.7
> > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > intel-2.7/_openssl.o
> >
> > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error: conflicting
> > types for 'BIO_new_mem_buf'
> >
> > BIO *BIO_new_mem_buf(void *, int);
> >
> >      ^
> >
> > /usr/local/opt/openssl/include/openssl/bio.h:692:6: note: previous
> > declaration is here
> >
> > BIO *BIO_new_mem_buf(const void *buf, int len);
> >
> >      ^
> >
> > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15: error:
> redefinition
> > of 'SSLv2_method' as different kind of symbol
> >
> > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> >
> >               ^
> >
> > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note: previous
> > definition is here
> >
> > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> >
> >                   ^
> >
> > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15: error:
> redefinition
> > of 'SSLv2_client_method' as different kind of symbol
> >
> > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> >
> >               ^
> >
> > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note: previous
> > definition is here
> >
> > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
> >
> >                   ^
> >
> > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15: error:
> redefinition
> > of 'SSLv2_server_method' as different kind of symbol
> >
> > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> >
> >               ^
> >
> > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note: previous
> > definition is here
> >
> > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
> >
> >                   ^
> >
> > 4 errors generated.
> >
> > error: command 'clang' failed with exit status 1
> >
> >
> > Jon
> > --
> >
> > Jon
> >
> > Sent from my mobile device
> >
>

Reply via email to