As i said since my machine was not having openssl1.0.1 installed, hence we 
need to build openssl first from source which gets installed at /usr/local/ 
where these libssl.so gets placed at /usr/local/lib64 and its link also 
gets created with the name libcrypto.so.1.0.0,  libssl.so.1.0.0

I restarted my Apache before adding the repository, its seems review board 
when try to perform p4.connect and it couldn't per that steps and reports 
errors.

If am able to perform p4.connect from outside, which P4API.so does review 
board referring to.

 
 
On Tuesday, April 9, 2013 12:38:26 PM UTC+5:30, Christian Hammond wrote:
>
> These e-mails keep ending up directed to me. Let's be sure they're all on 
> the mailing list.
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com <javascript:>
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
>  
> On Apr 9, 2013, at 12:05 AM, Christian Hammond 
> <chi...@chipx86.com<javascript:>> 
> wrote:
>
> Sorry, but what generates libssl.so?
>
> Just to be sure, did you restart Apache before adding a repository?
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com <javascript:>
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
>  
> On Apr 8, 2013, at 11:09 PM, chuck j <cjerr...@gmail.com <javascript:>> 
> wrote:
>
>
> Ok All the P4.* files are present in
>
> /usr/local/lib/python2.7/site-packages
>
> The libssl.so placed at /usr/local/lib64/libcrypto.so 
> /usr/local/lib64/libssl.so
>
> Do i need to do some manually changes in reviewboard setting which should 
> pick correct P4API.so
>
>
> On Tuesday, April 9, 2013 11:11:39 AM UTC+5:30, Christian Hammond wrote:
>>
>> Yeah, it's possible it's grabbing that one instead.
>>
>> If p4python is successfully built using OpenSSL, the only thing I can 
>> think of to cause that error would be Review Board using an older copy 
>> somehow.
>>
>> Where's the new P4.* files?
>>
>> Christian
>>
>> -- 
>> Christian Hammond - chi...@chipx86.com
>> Review Board - http://www.reviewboard.org
>> Beanbag, Inc. - http://www.beanbaginc.com
>>  
>> On Apr 8, 2013, at 10:39 PM, chuck j <cjerr...@gmail.com> wrote:
>>
>> Here are some more information:
>>
>> I can see there was old P4Python-2008.2-py2.7.egg-info file present at 
>> site-packages folder, But i had make sure this version's P4.py, P4.pyc, 
>> P4.pyo, P4API.so are moved to some safe place. Will this file make any 
>> difference.
>>
>> cat easy-install.pth
>>
>> import sys; sys.__plen = len(sys.path)
>> ./setuptools-0.6c11-py2.7.egg
>> ./python_memcached-1.47-py2.7.egg
>> ./recaptcha_client-1.0.6-py2.7.egg
>> ./python_dateutil-1.5-py2.7.egg
>> ./flup-1.0.3.dev_20110405-py2.7.egg
>> ./PIL-1.1.6-py2.7-linux-x86_64.egg
>> ./python_ldap-2.3.13-py2.7-linux-x86_64.egg
>> ./MySQL_python-1.2.3-py2.7-linux-x86_64.egg
>> ./ReviewBoard-1.7.6-py2.7.egg
>> ./pytz-2013b-py2.7.egg
>> ./Pygments-1.6-py2.7.egg
>> ./paramiko-1.10.0-py2.7.egg
>> ./mimeparse-0.1.3-py2.7.egg
>> ./Markdown-2.3.1-py2.7.egg
>> ./docutils-0.10-py2.7.egg
>> ./django_pipeline-1.2.24-py2.7.egg
>> ./Djblets-0.7.11-py2.7.egg
>> ./django_evolution-0.6.9-py2.7.egg
>> ./Django-1.4.5-py2.7.egg
>> ./pycrypto-2.6-py2.7-linux-x86_64.egg
>> ./feedparser-5.1.3-py2.7.egg
>> import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; 
>> p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = 
>> p+len(new)
>>
>>
>> On Tuesday, April 9, 2013 10:39:52 AM UTC+5:30, chuck j wrote:
>>>
>>> Hi Chris,
>>>
>>> Reviewboard is using the same version of python for which i have 
>>> provided example as below
>>>
>>> [GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] on linux2
>>> Type "help", "copyright", "credits" or "license" for more information.
>>> >>> import P4
>>>
>>> There are no Two version of p4python installed, how do i figure it out. 
>>> i can see my site-packages contains following files after p4python build 
>>> and install i.e P4.py, P4.pyc, P4.pyo, P4API.so
>>>
>>>
>>> On Tuesday, April 9, 2013 12:45:35 AM UTC+5:30, Christian Hammond wrote:
>>>>
>>>> Is Review Board using the same version of Python? Any chance there are 
>>>> now two copies of p4python installed?
>>>>
>>>> Christian
>>>>
>>>>
>>>> On Apr 8, 2013, at 4:01, chuck j <cjerr...@gmail.com> wrote:
>>>>
>>>> Dear All, 
>>>>
>>>> This is very critical, I am still not able to add SSL enabled perforce 
>>>> repository to reviewboard, Please help me.
>>>>
>>>> Since my machine was not having openssl 1.0.1, i need to build and 
>>>> install this version of openssl.
>>>>
>>>> I followed the instruction from document, downloaded openssl 1.0.1e
>>>>
>>>> ./config --prefix=/usr/local --openssldir=/usr/local/openssl zlib 
>>>> zlib-dynamic shared
>>>> make 
>>>> make test
>>>> make install
>>>>
>>>> Then i did following step
>>>>
>>>> Edit /etc/ld.so.conf
>>>>
>>>> add to paths...
>>>> /usr/local/lib64
>>>>
>>>> Update the run-time linker...
>>>> # ldconfig
>>>>
>>>> verified with below command:
>>>>
>>>> ldd /usr/local/bin/openssl
>>>>         libssl.so.1.0.0 => /usr/local/lib64/libssl.so.1.0.0 
>>>> (0x00002b08a088c000)
>>>>         libcrypto.so.1.0.0 => /usr/local/lib64/libcrypto.so.1.0.0 
>>>> (0x00002b08a0af1000)
>>>>         libdl.so.2 => /lib64/libdl.so.2 (0x0000003b2ac00000)
>>>>         libc.so.6 => /lib64/libc.so.6 (0x0000003b2a400000)
>>>>         /lib64/ld-linux-x86-64.so.2 (0x0000003b2a000000)
>>>>
>>>>
>>>> /usr/local/bin/openssl version
>>>>
>>>> OpenSSL 1.0.1e 11 Feb 2013
>>>>
>>>>
>>>> Then I build p4python with --ssl swtich.
>>>>
>>>> python setup.py build --apidir /root/work/src/p4api-2012.2.585708 --ssl 
>>>> /usr/local/lib64
>>>>
>>>> API Release 2012.2
>>>> running build
>>>> running build_py
>>>> creating build
>>>> creating build/lib.linux-x86_64-2.7
>>>> copying P4.py -> build/lib.linux-x86_64-2.7
>>>> running build_ext
>>>> building 'P4API' extension
>>>> creating build/temp.linux-x86_64-2.7
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c P4API.cpp -o 
>>>> build/temp.linux-x86_64-2.7/P4API.o -DOS_LINUX -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c PythonClientAPI.cpp -o 
>>>> build/temp.linux-x86_64-2.7/PythonClientAPI.o -DOS_LINUX -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c PythonClientUser.cpp -o 
>>>> build/temp.linux-x86_64-2.7/PythonClientUser.o -DOS_LINUX -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c SpecMgr.cpp -o 
>>>> build/temp.linux-x86_64-2.7/SpecMgr.o -DOS_LINUX -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c P4Result.cpp -o 
>>>> build/temp.linux-x86_64-2.7/P4Result.o -DOS_LINUX -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c PythonMergeData.cpp -o 
>>>> build/temp.linux-x86_64-2.7/PythonMergeData.o -DOS_LINUX -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c P4MapMaker.cpp -o 
>>>> build/temp.linux-x86_64-2.7/P4MapMaker.o -DOS_LINUX -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c PythonSpecData.cpp -o 
>>>> build/temp.linux-x86_64-2.7/PythonSpecData.o -DOS_LINUX -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c PythonMessage.cpp -o 
>>>> build/temp.linux-x86_64-2.7/PythonMessage.o -DOS_LINUX -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c PythonActionMergeData.cpp -o 
>>>> build/temp.linux-x86_64-2.7/PythonActionMergeData.o -DOS_LINUX 
>>>> -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall 
>>>> -Wstrict-prototypes -fPIC -DID_OS="LINUX26X86_64" -DID_REL="2012.2" 
>>>> -DID_PATCH="549493" -DID_API="2012.2/585708" -DID_Y="2012" -DID_M="11" 
>>>> -DID_D="05" -I/root/work/src/p4api-2012.2.585708 
>>>> -I/root/work/src/p4api-2012.2.585708/include/p4 
>>>> -I/usr/local/include/python2.7 -c PythonClientProgress.cpp -o 
>>>> build/temp.linux-x86_64-2.7/PythonClientProgress.o -DOS_LINUX -DOS_LINUX26 
>>>> -DOS_LINUXX86_64 -DOS_LINUX26X86_64
>>>> cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
>>>> for Ada/C/ObjC but not for C++
>>>> g++ -pthread -shared build/temp.linux-x86_64-2.7/P4API.o 
>>>> build/temp.linux-x86_64-2.7/PythonClientAPI.o 
>>>> build/temp.linux-x86_64-2.7/PythonClientUser.o 
>>>> build/temp.linux-x86_64-2.7/SpecMgr.o 
>>>> build/temp.linux-x86_64-2.7/P4Result.o 
>>>> build/temp.linux-x86_64-2.7/PythonMergeData.o 
>>>> build/temp.linux-x86_64-2.7/P4MapMaker.o 
>>>> build/temp.linux-x86_64-2.7/PythonSpecData.o 
>>>> build/temp.linux-x86_64-2.7/PythonMessage.o 
>>>> build/temp.linux-x86_64-2.7/PythonActionMergeData.o 
>>>> build/temp.linux-x86_64-2.7/PythonClientProgress.o 
>>>> -L/root/work/src/p4api-2012.2.585708 
>>>> -L/root/work/src/p4api-2012.2.585708/lib -L/usr/local/lib64 
>>>> -L/usr/local/lib -lclient -lrpc -lsupp -lssl -lcrypto -lrt -lpython2.7 -o 
>>>> build/lib.linux-x86_64-2.7/P4API.so
>>>>
>>>>
>>>> -----
>>>>
>>>> python setup.py install --apidir /root/work/src/p4api-2012.2.585708 
>>>> --ssl /usr/local/lib64
>>>> API Release 2012.2
>>>> running install
>>>> running build
>>>> running build_py
>>>> running build_ext
>>>> running install_lib
>>>> copying build/lib.linux-x86_64-2.7/P4API.so -> 
>>>> /usr/local/lib/python2.7/site-packages
>>>> running install_egg_info
>>>> Removing 
>>>> /usr/local/lib/python2.7/site-packages/p4python-2012.2.549493-py2.7.egg-info
>>>> Writing 
>>>> /usr/local/lib/python2.7/site-packages/p4python-2012.2.549493-py2.7.egg-info
>>>>
>>>> -----
>>>>
>>>> I tested with by connecting to ssl enabled perforce server. here are 
>>>> the steps.
>>>>
>>>> [GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] on linux2
>>>> Type "help", "copyright", "credits" or "license" for more information.
>>>> >>> import P4
>>>> >>> p4=P4.P4(client="myclient", port="ssl:p4-server:19773")
>>>> >>> print p4
>>>> P4 [root@myclient ssl:p4-perforce:19773] disconnected
>>>> >>> p4.connect()
>>>> P4 [root@myclient ssl:p4-perforce:19773] connected
>>>>
>>>> Then i try to add this repository through reviewboard admin panel, i am 
>>>> getting this error message
>>>>
>>>>  Please correct the error below.
>>>>
>>>>     The specified Perforce port includes ssl:, but the p4python library 
>>>> was built without SSL support or the system library path is incorrect. 
>>>>
>>>> Do you still see any issue with p4python build and install.
>>>>
>>>> If i am able to connect ssl enabled perforce server through python 
>>>> using P4 then, I guess reviewboard API should also be working accordingly, 
>>>> please advice me what should be the issue here. This SSL feature is 
>>>> holding 
>>>> my whole setup to complete.
>>>>
>>>> Please help to resolve this issue.
>>>>
>>>> let me know if you need any other log.
>>>>
>>>> -Chuck.
>>>>
>>>> -- 
>>>> Want to help the Review Board project? Donate today at 
>>>> http://www.reviewboard.org/donate/
>>>> Happy user? Let us know at http://www.reviewboard.org/users/
>>>> -~----------~----~----~----~------~----~------~--~---
>>>> To unsubscribe from this group, send email to 
>>>> reviewboard...@googlegroups.com
>>>> For more options, visit this group at 
>>>> http://groups.google.com/group/reviewboard?hl=en
>>>> --- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "reviewboard" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to reviewboard...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>  
>>>>  
>>>>
>>>>
>> -- 
>> Want to help the Review Board project? Donate today at 
>> http://www.reviewboard.org/donate/
>> Happy user? Let us know at http://www.reviewboard.org/users/
>> -~----------~----~----~----~------~----~------~--~---
>> To unsubscribe from this group, send email to 
>> reviewboard...@googlegroups.com
>> For more options, visit this group at 
>> http://groups.google.com/group/reviewboard?hl=en
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>>
>>
>
>

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to