So, I figured out how to make a new libssl and libcrypt - as a way to "fix"
a lot of failed tests, and as I would rather leave the original files in
/usr/lib and add new ones in /opt/lib - what flag am I missing (and should
I have asked this in "users") so the the modules ALSO use the same LIBPATH.
I would have expected them to have the same as the core.
core uses: /opt/lib:/usr/vac/lib:/usr/lib:/lib
as expected while the modules (more specifically, mod_ssl) does not look
/opt/lib at all!
mod_ssl.so uses: /usr/include/openssl/lib:/usr/vac/lib:/usr/lib:/lib
Note: there is no such directory /usr/include/openssl/lib - configure (or
libtool) seems to be inventing that.
DUMP comand output - complete.
root@x093:[/]dump -H /opt/httpd/sbin/httpd
/opt/httpd/sbin/httpd:
***Loader Section***
Loader Header Information
VERSION# #SYMtableENT #RELOCent LENidSTR
0x00000001 0x0000041e 0x00000c88 0x00000095
#IMPfilID OFFidSTR LENstrTBL OFFstrTBL
0x00000007 0x0000f950 0x000054dc 0x0000f9e5
***Import File Strings***
INDEX PATH BASE
MEMBER
0
/opt/lib:/usr/vac/lib:/usr/lib:/lib
1 libpcre.a
libpcre.so.1
2
libaprutil-1.so
3
libapr-1.so
4 libpthread.a
shr_xpg5.o
5 libc.a
shr.o
6 librtl.a
shr.o
root@x093:[/]dump -H /opt/httpd/lib*/mod_ssl*
/opt/httpd/libexec/mod_ssl.so:
***Loader Section***
Loader Header Information
VERSION# #SYMtableENT #RELOCent LENidSTR
0x00000001 0x000001c4 0x00000451 0x00000083
#IMPfilID OFFidSTR LENstrTBL OFFstrTBL
0x00000005 0x00005e4c 0x00002128 0x00005ecf
***Import File Strings***
INDEX PATH BASE
MEMBER
0
/usr/include/openssl/lib:/usr/vac/lib:/usr/lib:/lib
1 libssl.a
libssl.so.0.9.8
2 libcrypto.a
libcrypto.so.0.9.8
3 libc.a
shr.o
4
..
On Sun, Aug 3, 2014 at 4:35 PM, Michael Felt <mamf...@gmail.com> wrote:
> Thanks. So, when the t/TEST has a line with NOK: in it, there should be an
> error: in there I expect.
> FYI: most of what I am seeing are ssl related, but the vanilla ssh on AIX
> 5.3 TL7 is from 2009, so that is probably not surprising. (Going to
> investigate "inserting" a new openssl library and see if sshd still works
> as well as fewer t/TEST errors.)
>
>
> On Sun, Aug 3, 2014 at 3:03 PM, Eric Covener <cove...@gmail.com> wrote:
>
>> On Sun, Aug 3, 2014 at 7:50 AM, Michael Felt <mamf...@gmail.com> wrote:
>> > A couple of time I have gotten started with using test from Apache.
>> >
>> > Just to be clear about how I am starting I use svn to get the latest
>> sources
>> > and have test and test/ApacheTest from
>> >
>> > ./svn/bin/jsvn checkout
>> > http://svn.apache.org/repos/asf/httpd/test/framework/trunk
>> > /data/prj/apache/httpd/test
>> > echo Apache-Test starting
>> > ./svn/bin/jsvn checkout
>> > http://svn.apache.org/repos/asf/perl/Apache-Test/trunk
>> > /data/prj/apache/httpd/test/Apache-Test
>>
>> I only checkout
>> https://svn.apache.org/repos/asf/httpd/test/framework/trunk and my SVN
>> client fetches the other as an external (I think, it just works)
>>
>> > 1) should Apache-Test be a subdirectory (does "test" recognize that and
>> use
>> > it on some way - or is that a separate test intended only/mainly for
>> > mod_perl). Apache-Test as a project page does not say much.
>>
>> It's for everything and it ends up a subdirectory
>>
>> > 2) what are the vital lines to look for in .../test/t/logs/error_log (or
>> > what is the difference between :alert and :error lines)?
>>
>> It's just a severity. Alert is more severe than error. You would only
>> check the error_log if you were chasing down a failed test
>>
>> (you can also ./testall -v foo/bar.t to sometimes get more info)
>>
>> --
>> Eric Covener
>> cove...@gmail.com
>>
>
>
