Date: Mon, 17 Dec 2012 15:34:37 +0100 (CET) From: Martin Olsson <martin.olsson@sentor.se> To: araujo@FreeBSD.org Cc: ports@FreeBSD.org Subject: FreeBSD Port: www/mod_security (ap22-mod_security-2.6.6) Message-ID: <alpine.BSF.2.00.1212171452340.61290@farmermaggot.shire.sentor.se> In-Reply-To: <alpine.BSF.2.00.1212171155180.61290@farmermaggot.shire.sentor.se> References: <011401cdd9f2$730d7ff0$59287fd0$@sentor.se> <alpine.BSF.2.00.1212140713340.58638@wonkity.com> <alpine.BSF.2.00.1212171023370.61290@farmermaggot.shire.sentor.se> <alpine.BSF.2.00.1212171155180.61290@farmermaggot.shire.sentor.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi araujo!
I think something is wrong with ap22-mod_security-2.6.6.
As you saw in my previous email, I get the options dialog again after
first running 'portmaster -na' and answering all dialogs.
I now tried a rebuild of www/mod_security where I force the creation of
configs.
I run 'portmaster --force-config -dgf www/mod_security'.
I now get option dialogs for all depending ports and for ap22-mod_security
2.6.6_1. I press tab and enter to accept the defaults to all of them.
(for ap22-mod_security this mean: [ ] LUA and [ ] MLOGC).
Ports are now being built. (libcrypto, openssl, pcre, libxml,
apache22-2.2.23_3, etc)
Suddenly I get the options dialog for ap22-mod_security-2.6.6 again.
I press tab and enter to accept the defaults once more ([ ] LUA and
[ ] MLOGC).
It continues building...
...
...
===> Extracting for ap22-mod_security-2.6.6_1
=> SHA256 Checksum OK for modsecurity-apache_2.6.6.tar.gz.
===> Patching for ap22-mod_security-2.6.6_1
===> ap22-mod_security-2.6.6_1 depends on file: /usr/local/sbin/apxs - found
===> ap22-mod_security-2.6.6_1 depends on executable: pkgconf - found
===> ap22-mod_security-2.6.6_1 depends on shared library: pcre.3 - found
===> ap22-mod_security-2.6.6_1 depends on shared library: apr-1 - found
===> ap22-mod_security-2.6.6_1 depends on shared library: xml2.5 - found
===> Configuring for ap22-mod_security-2.6.6_1
checking for a BSD-compatible install... /usr/bin/install -c -o root -g
wheel
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... build/install-sh -c -d
checking for gawk... no
...
...
===> Building for ap22-mod_security-2.6.6_1
Making all in tools
Making all in apache2
...
...
Suddenly I get the options dialog for ap22-mod_security-2.6.6 a third
time! I press tab and enter to accept the defaults once more ([ ] LUA and
[ ] MLOGC).
After this dialog I see this on the screen:
===> Installing for ap22-mod_security-2.6.6_1
===> Generating temporary packing list
===> Checking if www/mod_security already installed
Making install in tools
test -z "/usr/local/bin" || ../build/install-sh -c -d "/usr/local/bin"
install -o root -g wheel -m 555 rules-updater.pl '/usr/local/bin'
Making install in apache2
test -z "/usr/local/lib" || ../build/install-sh -c -d "/usr/local/lib"
/bin/sh ../libtool --mode=install /usr/bin/install -c -o root -g wheel
mod_security2.la '/usr/local/lib'
libtool: install: /usr/bin/install -c -o root -g wheel
.libs/mod_security2.so /usr/local/lib/mod_security2.so
libtool: install: /usr/bin/install -c -o root -g wheel
.libs/mod_security2.lai /usr/local/lib/mod_security2.la
libtool: install: /usr/bin/install -c -o root -g wheel
.libs/mod_security2.a /usr/local/lib/mod_security2.a
libtool: install: chmod 644 /usr/local/lib/mod_security2.a
libtool: install: ranlib /usr/local/lib/mod_security2.a
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,-rpath -Wl,LIBDIR' linker flag
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
/usr/bin/make install-exec-hook
Removing unused static libraries...
Making install in tests
install -o root -g wheel -m 444
/usr/ports/www/mod_security/work/modsecurity-apache_2.6.6/modsecurity.conf-recommended
/usr/local/etc/modsecurity.conf-example
===> Registering installation for ap22-mod_security-2.6.6_1
===>>> Creating a package for new version ap22-mod_security-2.6.6_1
That's it. Here the process freezes. :-(
Nothing happen and nothing new is displayed on screen.
I switch to another shell and list the processes:
-- /usr/local/bin/bash
`-- /bin/sh /usr/local/sbin/portmaster --force-config -dgf www/mod_security
`-- /usr/bin/make package
`-- /bin/sh -ec cd /usr/ports/www/mod_security && /usr/bin/make do-config;
`-- /usr/bin/make do-config
`-- [sh]
`-- /usr/bin/dialog --checklist Options for ap22-mod_security 2.6.6_1 21 70 15 LUA Embedded Lua language support off MLOGC Build ModSecurity Log Collector off
So there is a dialog process running, but I don't see any dialog!
I switch back to the 'portmaster' shell and press <tab> and <enter> in the
blind (after the line "===>>> Creating a package for new version
ap22-mod_security-2.6.6_1").
Apparently my keystrokes are received by that hidden dialog process,
'cause the 'portmaster' command now continues:
===>>> Package saved to /usr/ports/packages/All
===>>> pkg-message for python27-2.7.3_3
====
Note that some of the standard modules are provided as separate
ports since they require extra dependencies:
bsddb databases/py-bsddb
gdbm databases/py-gdbm
sqlite3 databases/py-sqlite3
tkinter x11-toolkits/py-tkinter
Install them as needed.
====
===>>> pkg-message for openssl-1.0.1_4
Copy /usr/local/openssl/openssl.cnf.sample to
/usr/local/openssl/openssl.cnf
and edit it to fit your needs.
===>>> pkg-message for apache22-2.2.23_3
To run apache www server from startup, add apache22_enable="YES"
in your /etc/rc.conf. Extra options can be found in startup script.
Your hostname must be resolvable using at least 1 mechanism in
/etc/nsswitch typically DNS or /etc/hosts or apache might
have issues starting depending on the modules you are using.
===>>> Done displaying pkg-message files
===>>> The following actions were performed:
Re-installation of libtool-2.4.2
Re-installation of libiconv-1.14
Re-installation of db42-4.2.52_5
Re-installation of gettext-0.18.1.1
Re-installation of gmake-3.82_1
Re-installation of gdbm-1.9.1
Re-installation of xz-5.0.3
Re-installation of m4-1.4.16_1,1
Re-installation of perl-5.16.2
Re-installation of help2man-1.40.13
Re-installation of autoconf-wrapper-20101119
Re-installation of autoconf-2.69
Re-installation of automake-wrapper-20101119
Re-installation of automake-1.12.5
Re-installation of python27-2.7.3_3
Re-installation of pkgconf-0.8.9
Re-installation of xproto-7.0.22
Re-installation of makedepend-1.0.3,1
Re-installation of openssl-1.0.1_4
Re-installation of expat-2.0.1_2
Re-installation of apr-1.4.6.1.4.1_3
Re-installation of pcre-8.32
Re-installation of libxml2-2.7.8_5
Re-installation of apache22-2.2.23_3
Re-installation of ap22-mod_security-2.6.6_1
...and the 'portmaster' command finishes.
Do you have any idea as to what is going on? I have never experienced
anything simillar.
/Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1212171452340.61290>