Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev <gentoo-dev@g.o>
From: Andrew Cowie <andrew@...>
Subject: Detecting gcj in ebuilds
Date: Thu, 11 Nov 2004 10:54:26 +1100
Is there a Gentoo Way (tm) for testing whether a specific language
module is available in gcc?

++

The specific case is gcj - I had "gcj" in my use flags from way back,
but I just got a field report from someone testing an ebuild I've
prepared saying:

> it didnt work at first, fell over in the libgtk-java install, but i
> figured out that i had to emerge gcc with gcj support, then I did
> emerge java-gnome and it all worked. Top class. Thanks again.

My ebuilds respond to USE=gcj, but I obviously need to do a dependency
type check. Obviously something like 

	test -x `which gcj`

Would serve, but is there some magic (gcc-config or better yet a
dependency?) which would help?

[It's almost like there should be something like virtual/gcj provided by
gcc if gcc is compiled with Java enabled... Hm]

AfC
Sydney

-- 
Andrew Frederick Cowie
Principal
Operational Dynamics Consulting Pty Ltd

Helping you succeed at flawlessly executing Massive
Changes and Upgrades to your Mission Critical Systems
http://www.operationaldynamics.com/infrastructure/

Sydney   New York   Toronto   London
Attachment:
signature.asc (This is a digitally signed message part)
Replies:
Re: Detecting gcj in ebuilds
-- Mike Frysinger
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
staffing needs
Next by thread:
Re: Detecting gcj in ebuilds
Previous by date:
staffing needs
Next by date:
Re: Detecting gcj in ebuilds


Updated Oct 31, 2011

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.