From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] Can't emerge HTML-Mason
Date: Tue, 4 Apr 2006 08:11:29 -0400 [thread overview]
Message-ID: <200604040811.29565.mcummings@gentoo.org> (raw)
In-Reply-To: <b75f05a10604040455h5a1c85fdvb078431b3b8adb7e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
Yeah, this falls into the category of my messsing up the perl-module eclass.
Everyone should be happy campers again, and HTML-Mason should only fail for
legitimate reasons now :)
On Tuesday 04 April 2006 07:55, wernerus sebastien wrote:
> Yes, it was indeed related to this bug. Mason compile fine now. Thanks
>
> On 4/4/06, Christian Hartmann <ian@gentoo.org> wrote:
> > > !!! ERROR: dev-perl/HTML-Mason-1.32 failed.
> > > Call stack:
> > > ebuild.sh, line 1526: Called dyn_compile
> > > ebuild.sh, line 923: Called src_compile
> > > ebuild.sh, line 1236: Called perl-module_src_compile
> > > perl-module.eclass, line 127: Called die
> >
> > Please `emerge --sync` and try again. Looks like your problem is related
> > to the perl-module.eclass problems reported in bug 128487.
> >
> > [1] https://bugs.gentoo.org/show_bug.cgi?id=128487
> >
> > Regards,
> > Christian Hartmann
> > http://www.gentoo.org/~ian/
> >
> > PGP Key:
> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2154E5EE692A4865
> > Key fingerprint = 4544 EC0C BAE4 216F 5981 7F95 2154 E5EE 692A 4865
> >
> > --
> > gentoo-perl@gentoo.org mailing list
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-04-04 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 11:17 [gentoo-perl] Can't emerge HTML-Mason wernerus sebastien
2006-04-04 11:34 ` Christian Hartmann
2006-04-04 11:55 ` wernerus sebastien
2006-04-04 12:11 ` Michael Cummings [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200604040811.29565.mcummings@gentoo.org \
--to=mcummings@gentoo.org \
--cc=gentoo-perl@gentoo.org \
--cc=gentoo-perl@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox