Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 789966 - x11-libs/pango-1.48.4-r1 will not compile
Summary: x11-libs/pango-1.48.4-r1 will not compile
Status: RESOLVED DUPLICATE of bug 463976
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-13 13:56 UTC by peter@prh.myzen.co.uk
Modified: 2021-05-13 22:37 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge info =x11-libs/pango-1.48.4-r1 (pango.info,6.20 KB, text/plain)
2021-05-13 13:56 UTC, peter@prh.myzen.co.uk
Details
Emerge log (pango.log,181.86 KB, text/plain)
2021-05-13 13:56 UTC, peter@prh.myzen.co.uk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description peter@prh.myzen.co.uk 2021-05-13 13:56:03 UTC
Created attachment 708069 [details]
emerge info =x11-libs/pango-1.48.4-r1

Installing an ~amd64 system from scratch, following the handbook, I get as far as the first emerge -uaDvN @world, during which pango fails with a ninja no-can-do error. Info and log attached.
Comment 1 peter@prh.myzen.co.uk 2021-05-13 13:56:43 UTC
Created attachment 708072 [details]
Emerge log
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-05-13 13:59:09 UTC
>Can't locate Locale/gettext.pm in @INC (you may need to install the Locale::gettext module) (@INC contains: /etc/perl /usr/local/lib64/perl5/5.32/x86_64-linux /usr/local/lib64/perl5/5.32 /usr/lib64/perl5/vendor_perl/5.32/x86_64-linux /usr/lib64/perl5/vendor_perl/5.32 /usr/lib64/perl5/5.32/x86_64-linux /usr/lib64/perl5/5.32 /usr/lib64/perl5/5.30.3 /usr/lib64/perl5/vendor_perl/5.30.3) at /usr/bin/help2man line 30.
BEGIN failed--compilation aborted at /usr/bin/help2man line 30.

I suspect you've added some USE flag to make.conf and this has caused a flag to be flipped on Perl.

It should normally give a message after installing Perl to run perl-cleaner.

Can you run perl-cleaner --all for me?
Comment 3 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-05-13 14:00:25 UTC

*** This bug has been marked as a duplicate of bug 463976 ***
Comment 4 peter@prh.myzen.co.uk 2021-05-13 20:51:22 UTC
(In reply to Sam James from comment #2)
> >Can't locate Locale/gettext.pm in @INC (you may need to install the Locale::gettext module) (@INC contains: /etc/perl /usr/local/lib64/perl5/5.32/x86_64-linux /usr/local/lib64/perl5/5.32 /usr/lib64/perl5/vendor_perl/5.32/x86_64-linux /usr/lib64/perl5/vendor_perl/5.32 /usr/lib64/perl5/5.32/x86_64-linux /usr/lib64/perl5/5.32 /usr/lib64/perl5/5.30.3 /usr/lib64/perl5/vendor_perl/5.30.3) at /usr/bin/help2man line 30.
> BEGIN failed--compilation aborted at /usr/bin/help2man line 30.
> 
> I suspect you've added some USE flag to make.conf and this has caused a flag
> to be flipped on Perl.
> 
> It should normally give a message after installing Perl to run perl-cleaner.
> 
> Can you run perl-cleaner --all for me?

Running perl-cleaner resulted in 39 reinstallations, after which the emerge ran its course.

Running 'grep -r perl /etc/portage' returns a null result.
Comment 5 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-05-13 21:12:29 UTC
(In reply to peter@prh.myzen.co.uk from comment #4)
> (In reply to Sam James from comment #2)
> > >Can't locate Locale/gettext.pm in @INC (you may need to install the Locale::gettext module) (@INC contains: /etc/perl /usr/local/lib64/perl5/5.32/x86_64-linux /usr/local/lib64/perl5/5.32 /usr/lib64/perl5/vendor_perl/5.32/x86_64-linux /usr/lib64/perl5/vendor_perl/5.32 /usr/lib64/perl5/5.32/x86_64-linux /usr/lib64/perl5/5.32 /usr/lib64/perl5/5.30.3 /usr/lib64/perl5/vendor_perl/5.30.3) at /usr/bin/help2man line 30.
> > BEGIN failed--compilation aborted at /usr/bin/help2man line 30.
> > 
> > I suspect you've added some USE flag to make.conf and this has caused a flag
> > to be flipped on Perl.
> > 
> > It should normally give a message after installing Perl to run perl-cleaner.
> > 
> > Can you run perl-cleaner --all for me?
> 
> Running perl-cleaner resulted in 39 reinstallations, after which the emerge
> ran its course.

It's possible you set a general USE flag in make.conf which flipped a USE flag on Perl, but also possible it was bad luck - see the bug I marked this as a dupe of.

> 
> Running 'grep -r perl /etc/portage' returns a null result.
Comment 6 peter@prh.myzen.co.uk 2021-05-13 22:29:59 UTC
(In reply to Sam James from comment #5)
> (In reply to peter@prh.myzen.co.uk from comment #4)
> > (In reply to Sam James from comment #2)
> > > >Can't locate Locale/gettext.pm in @INC (you may need to install the Locale::gettext module) (@INC contains: /etc/perl /usr/local/lib64/perl5/5.32/x86_64-linux /usr/local/lib64/perl5/5.32 /usr/lib64/perl5/vendor_perl/5.32/x86_64-linux /usr/lib64/perl5/vendor_perl/5.32 /usr/lib64/perl5/5.32/x86_64-linux /usr/lib64/perl5/5.32 /usr/lib64/perl5/5.30.3 /usr/lib64/perl5/vendor_perl/5.30.3) at /usr/bin/help2man line 30.
> > > BEGIN failed--compilation aborted at /usr/bin/help2man line 30.
> > > 
> > > I suspect you've added some USE flag to make.conf and this has caused a flag
> > > to be flipped on Perl.
> > > 
> > > It should normally give a message after installing Perl to run perl-cleaner.
> > > 
> > > Can you run perl-cleaner --all for me?
> > 
> > Running perl-cleaner resulted in 39 reinstallations, after which the emerge
> > ran its course.
> 
> It's possible you set a general USE flag in make.conf which flipped a USE
> flag on Perl, but also possible it was bad luck - see the bug I marked this
> as a dupe of.
> 
> > 
> > Running 'grep -r perl /etc/portage' returns a null result.

Please see the files I attached to the bug report. I can't see anything I've done like what you suggest.

I'd also like to point out that the failure was repeatable.
Comment 7 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-05-13 22:37:27 UTC
It wasn’t an accusation, I was just providing a pointer. But yeah, probably bad luck in the form of the bug I referenced then.

Bad luck in the sense that emerge schedules packages in the wrong order and it’s a frustrating bug for reasons you can read about, not an unreproducible problem :)