Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-perl
Navigation:
Lists: gentoo-perl: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-perl@g.o
From: Davide Angelocola <davide.angelocola@...>
Subject: www-server/mod_perl-2.0.3 ebuild
Date: Mon, 29 Jan 2007 11:21:29 +0100
Hi,
in the ebuild for mod_perl there is this code:
 if [ "${INSTALLED_MPM}" != "prefork" ]; then
        if [ "${ITHREADS}" == "undef" ]; then
            ewarn "You cannot build mod_perl on a threaded apache"
            ewarn "with an unthreaded perl. You must either emerge"
            ewarn "perl with ithreads in your USE flags, or emerge"
            ewarn "apache without threading support"
            exit
        fi
    fi

when I try to emerge it, with threated apache and unthreaded perl I got:
...
>>> Unpacking source...
 * You cannot build mod_perl on a threaded apache
 * with an unthreaded perl. You must either emerge
 * perl with ithreads in your USE flags, or emerge
 * apache without threading support
>>> Compiling source in /var/tmp/portage/www-apache/mod_perl-2.0.3 ...
Can't open perl script "Makefile.PL": No such file or directory

That is ok. However I think that "die" should be better than "exit" here in 
order to avoid the error "Can't open ...".

-- 
Best Regards,
Davide Angelocola
-- 
-- Davide Angelocola
-- 
gentoo-perl@g.o mailing list


Replies:
Re: www-server/mod_perl-2.0.3 ebuild
-- Michael Cummings
Navigation:
Lists: gentoo-perl: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
why different ebuilds for perl and libperl?
Next by thread:
Re: www-server/mod_perl-2.0.3 ebuild
Previous by date:
Perl ebuilds needing updates
Next by date:
[Patch] up2date-ng and CPAN package list


Updated Jun 17, 2009

Summary: Archive of the gentoo-perl mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.