From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] PORTAGE message
Date: Sat, 22 Jul 2006 18:43:36 -0700 [thread overview]
Message-ID: <9acccfe50607221843g412b1f10u4d285ffea34eae40@mail.gmail.com> (raw)
The ebuild for media-libs/libmpeg3-1.5.2 is giving me a message I don't
know how to use:
> WARN: prerm
> Please upgrade your package (libmpeg3-1.5.2) to use toolchain-funcs.eclass
>
> WARN: postrm
> Please upgrade your package (libmpeg3-1.5.2) to use toolchain-funcs.eclass
I don't know how to upgrade this any more than what I just did by emerging it.
Anybody know what it's talking about? Anybody even know what toolchain-funcs
it's talking about -- my browse through the portage tree comes up with
no obvious
candidate.
++ kevin
--
Kevin O'Gorman, PhD
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-07-23 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 1:43 Kevin O'Gorman [this message]
2006-07-23 2:35 ` [gentoo-user] PORTAGE message Iain Buchanan
2006-07-23 2:44 ` Ryan Tandy
2006-08-14 2:39 ` Kevin O'Gorman
2006-08-14 4:01 ` Hemmann, Volker Armin
2006-08-15 5:54 ` Kevin O'Gorman
2006-08-15 11:27 ` Hemmann, Volker Armin
2006-08-15 11:49 ` Bo Ørsted Andresen
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=9acccfe50607221843g412b1f10u4d285ffea34eae40@mail.gmail.com \
--to=kogorman@gmail.com \
--cc=gentoo-user@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