From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Finding GCC+GCJ greater than 3.4.2
Date: Sun, 24 Apr 2005 22:15:11 -0400 [thread overview]
Message-ID: <200504242215.11988.vapier@gentoo.org> (raw)
In-Reply-To: <87oec3ekhm.wl@badger.wordzoo.com>
On Sunday 24 April 2005 09:03 pm, Jared Rhine wrote:
> #pkg_setup() {
> # if [[ ! $(built_with_use gcc gcj) ]] ; then
> # eerror 'Chandler build requires that GCC be built with the "gcj"
> USE flag' # die "exiting because of GCJ dependency"
> # fi
> #}
first, that if statement is straight up wrong ... it should be (syntax wise):
if built_with_use gcc gcj ; then
to address the version issue, try something like:
local gccpkg=$(best_version '>=sys-devel/gcc-3.4.2')
if built_with_use ${gccpkg} gcj ; then
> My goal is to make this ebuild find and use a working GCC if it is
> present, even in the presence of slots and mixed use flags.
i'd say make the user run `gcc-config` themselves before emerging
-mike
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2005-04-25 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 1:03 [gentoo-dev] Finding GCC+GCJ greater than 3.4.2 Jared Rhine
2005-04-25 2:15 ` Mike Frysinger [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=200504242215.11988.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@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