On 19 Jan 2017, at 00:20, William A Rowe Jr <wr...@rowe-clan.net> wrote:
> On Wed, Jan 18, 2017 at 4:14 PM, Dirk-Willem van Gulik <di...@webweaving.org> > wrote: >> What is the right/proper way to test the crypto modules (as they are not >> copied into apr/.lib during a normal build) from 'test/testall’ ? > I think an LD_LIBRARY_PATH dance might be simplest? We try both the path/ > and the path/apr-#/ locations. Aye - it seems all a bit messy - not in the least because test/* picks up the libapr-2.la in the directory above it - and that file is alread primed for the actual install —prefix - not for the so/a files then (still in) apr/.libs and (especially) apr/crypto/.libs. So I am a bit struggling to find a simple/fast & cleanly contained tests cycles against the version ‘in-tree’. Was hoping for a known trick/flag, Dw