Am 27.02.2018 um 00:13 schrieb Alain Toussaint:
Hello,

I have a test log of trunk apr build with these configure settings:

./configure --prefix=/usr --disable-static --enable-nonportable-atomics 
--enable-threads --enable-
posix-shm --enable-allocator-uses-mmap --enable-allocator-guard-pages 
--with-gdbm=/usr --with-
openssl=/usr --with-crypto --with-installbuilddir=/usr/share/apr-dev/build 
--with-sqlite3=/usr --
with-libxml2=/usr

of particular note, the errors I'm getting are:

testlfs             : |Line 345: Large Files not supported

If you are doing a 64 bit build, this is likely just a misleading output message. See https://bz.apache.org/bugzilla/show_bug.cgi?id=45615 comment 4 and 5.

Regards,

Rainer

I'm compiling in a 16GB (half my ram) tmpfs on mode=0755,uid=0,gid=0 in 
/usr/src:

(lfs chroot) root:/usr/src/apr# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop0       16G  2.3G   13G  16% /
udev             16G     0   16G   0% /dev
tmpfs            16G     0   16G   0% /run
tmpfs            16G   22M   16G   1% /usr/src

the tmpfs might not support large file.

testcrypto below:

testcrypto          : |Line 50: Crypto driver 'openssl' DSO could not be opened
|Line 50: Crypto driver 'nss' DSO could not be opened
|Line 50: Crypto driver 'commoncrypto' DSO could not be opened
|Line 50: Crypto driver 'openssl' DSO could not be opened
-Line 50: Crypto driver 'openssl' DSO could not be opened
-Line 50: Crypto driver 'openssl' DSO could not be opened
\Line 50: Crypto driver 'openssl' DSO could not be opened
/Line 50: Crypto driver 'nss' DSO could not be opened
|Line 50: Crypto driver 'nss' DSO could not be opened
|Line 50: Crypto driver 'nss' DSO could not be opened
-Line 50: Crypto driver 'nss' DSO could not be opened
-Line 50: Crypto driver 'commoncrypto' DSO could not be opened
[snip]
SUCCESS

This is on OpenSSL 1.1.0g  2 Nov 2017. Any issues between apr-2 and openssl 
1.1.0g? I look at the
BLFS version 2018-02-26 page 
(http://linuxfromscratch.org/blfs/view/systemd/general/apr-util.html)
of apr-util and we don't need patches for apr-util-1.6.1

These are the only issues that I am having at the moment.

Alain

Reply via email to