mod_fcgid-2.1-r1 compiles fine, but when it comes to installation it spits following error: >>> Source compiled. >>> Test phase [not enabled]: www-apache/mod_fcgid-2.1-r1 >>> Install mod_fcgid-2.1-r1 into /var/tmp/portage/www-apache/mod_fcgid-2.1-r1/image/ category www-apache make[1]: Entering directory `/var/tmp/portage/www-apache/mod_fcgid-2.1-r1/work/mod_fcgid.2.1' /bin/sh: /var/tmp/portage/net-www/apache-2.0.58-r2/work/httpd-2.0.58/build/mkdir.sh: No such file or directory make[1]: *** [install-modules] Error 127 make[1]: Leaving directory `/var/tmp/portage/www-apache/mod_fcgid-2.1-r1/work/mod_fcgid.2.1' make: *** [install-recursive] Error 1 Reproducible: Always Steps to Reproduce: 1.emerge =www-apache/mod_fcgid-2.1-r1 2. 3. Actual Results: Well, failure :D I'm running stable apache 2.0.58-r2, and mod_fcgid-2.1 (no longer in portage) works fine.
This is a dup of the last two problems on bug 179597
This is what I get: >>> Install mod_fcgid-2.1-r1 into /var/tmp/portage/www-apache/mod_fcgid-2.1-r1/image/ category www-apache make[1]: Entering directory `/var/tmp/portage/www-apache/mod_fcgid-2.1-r1/work/mod_fcgid.2.1' mkdir /var/tmp/portage/www-apache/mod_fcgid-2.1-r1/image/usr mkdir /var/tmp/portage/www-apache/mod_fcgid-2.1-r1/image/usr/lib64 mkdir /var/tmp/portage/www-apache/mod_fcgid-2.1-r1/image/usr/lib64/apache2 mkdir /var/tmp/portage/www-apache/mod_fcgid-2.1-r1/image/usr/lib64/apache2/modules /bin/sh /usr/lib64/apache2/build/libtool --silent --mode=install cp mod_fcgid.la /var/tmp/portage/www-apache/mod_fcgid-2.1-r1/image//usr/lib64/apache2/modules/ /bin/sh: /usr/lib64/apache2/build/libtool: No such file or directory make[1]: *** [install-modules] Error 127 make[1]: Leaving directory `/var/tmp/portage/www-apache/mod_fcgid-2.1-r1/work/mod_fcgid.2.1' make: *** [install-recursive] Error 1 !!! ERROR: www-apache/mod_fcgid-2.1-r1 failed. Call stack: ebuild.sh, line 1621: Called dyn_install ebuild.sh, line 1067: Called qa_call 'src_install' ebuild.sh, line 44: Called src_install mod_fcgid-2.1-r1.ebuild, line 44: Called die
I was finally able to work around install issues of mod_fcgid-2.1-r1 with a quick'n'dirty solution: to create the missing /var/tmp/portage/net-www/apache-2.0.58-r2/work/httpd-2.0.58/build/mkdir.sh, it's ok to unpack the apache sources: ebuild /usr/portage/net-www/apache/apache-2.0.58-r2.ebuild unpack to create the missing /usr/lib64/apache2/build/libtool, it can be linked to /usr/bin/libtool: ln -s /usr/bin/libtool /usr/lib64/apache2/build/libtool. It's just a workaround. At least I can run mod_fcgid 2.1 now.
This problem is not in the mod_fcgid build, it's because the config_vars.mk file installed by the apache ebuild contains pointers to the wrong build tools. The apache ebuild should correct that file so that modules can trust it.
(In reply to comment #4) > This problem is not in the mod_fcgid build, it's because the config_vars.mk > file installed by the apache ebuild contains pointers to the wrong build tools. > The apache ebuild should correct that file so that modules can trust it. Care to enlighten me to what brokenness you're referring to ?
it refers to a non-existant libtool in /usr/share/apache/build (or some similar) the other problem is a harder one, because it refers to the source path of the apache build, which seems to assume that anyone who wants to install apache modules from source also has a full copy of the apache source code sitting around. this one I essentially hacked to point to the path containing mkdir.sh (apr-o something something) which worked, but I'm not sure it would work for all modules or on all systems
Created attachment 124555 [details, diff] Patch for mod_fcgid 2.1-r1 ebuild This patch will correct the wrong path on the ebuild, that makes the install phase impossible.
mod_fcgid-2.1-r2 does not use the makefile, but only apxs. should be fixed.
