You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Alain Toussaint <al...@vocatus.pub> on 2018/02/26 23:13:06 UTC
apr trunk make test results on LFS
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
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
Re: apr trunk make test results on LFS
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
Redirecting this first set of questions to the APR project.
Your LFS question is already answered.
The apr-2.0 / apr-util 1.6 bug you describe means that apr_crypto_openssl.so
and apr_crypto_nss.so modules were not built, or cannot be found in the test
path, but were expected to be built. I add --without-nss to keep apr(-util) from
being confused, and --without-ldap / --without-lber when compiling against
a specific openssl (system ldap packages bring in system openssl).
Both of these versions support OpenSSL 1.0.2 and 1.1.0, and aught to
support 1.1.1. I'm reviewing that support right at the moment.
(Please remember to reply-to-all for apr's dev list)
On Mon, Feb 26, 2018 at 5:13 PM, Alain Toussaint <al...@vocatus.pub> wrote:
> 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
>
> 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
Re: apr trunk make test results on LFS
Posted by Alain Toussaint <al...@vocatus.pub>.
> 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.
Indeed, it is a 64bit build. Forgot to add:
gcc 7.3.0 with retpoline, no multilib
binutils 2.30
glibc 2.27
At the moment, it's running under chroot on a debian 9.3 system. Kernel is
4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u2 (2018-02-21)
Alain
Re: apr trunk make test results on LFS
Posted by Rainer Jung <ra...@kippdata.de>.
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