Try the suggestions of bowei_99, but if you really want to nail down this problem, continue reading :)

Looking at the initial error message again, I see this important thing:

libapreq2.so.2: cannot open shared object file: No such file or directory

Let's check if your httpd binary has all libraries: 

ldd /usr/sbin/httpd

[download]
And check that there are no missing libraries in the output of ldd. BTW, is /usr/sbin/httpd your correct Apache binary?

Even if ldd of httpd locates all libraries, find where your libapreq2.so.2 is and add it to your LD_LIBRARY_PATH environment variable. 

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/path/of/your/libapreq2

[download]
Then try the "make test" again.

Note: setting the LD_LIBRARY_PATH variable is not recommended, I'm suggesting it here just for the sake of debugging.

In reply to Re^5: libapreq2 installtion by salvix
in thread libapreq2 installtion by smthames

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.