Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 829175 - x11-terms/mrxvt-0.5.4 - configure: WARNING: unrecognized options: --enable-kr
Summary: x11-terms/mrxvt-0.5.4 - configure: WARNING: unrecognized options: --enable-kr
Status: RESOLVED DUPLICATE of bug 829156
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Anthony Basile
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-14 14:09 UTC by Toralf Förster
Modified: 2022-03-26 01:16 UTC (History)
0 users

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


Attachments
emerge-history.txt (emerge-history.txt,357.91 KB, text/plain)
2021-12-14 14:09 UTC, Toralf Förster
Details
etc.portage.tar.bz2 (etc.portage.tar.bz2,23.96 KB, application/x-bzip)
2021-12-14 14:09 UTC, Toralf Förster
Details
x11-terms:mrxvt-0.5.4:20211214-115528.log (x11-terms:mrxvt-0.5.4:20211214-115528.log,34.53 KB, text/plain)
2021-12-14 14:09 UTC, Toralf Förster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster gentoo-dev 2021-12-14 14:09:04 UTC
configure: WARNING: unrecognized options: --enable-kr

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_hardened-j4-20211208-210004

  -------------------------------------------------------------------

  The log matches a QA pattern or a pattern requested by a Gentoo developer.
Comment 1 Toralf Förster gentoo-dev 2021-12-14 14:09:06 UTC
Created attachment 758940 [details]
emerge-history.txt
Comment 2 Toralf Förster gentoo-dev 2021-12-14 14:09:07 UTC
Created attachment 758941 [details]
etc.portage.tar.bz2
Comment 3 Toralf Förster gentoo-dev 2021-12-14 14:09:08 UTC
Created attachment 758942 [details]
x11-terms:mrxvt-0.5.4:20211214-115528.log
Comment 4 Toralf Förster gentoo-dev 2021-12-14 14:11:17 UTC

*** This bug has been marked as a duplicate of bug 829156 ***