-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Karl Trygve Kalleberg wrote:
> Petteri Räty wrote:
> 
> I don't see how symlinks in /usr/include can work. If there are two
> users on a system, each with his own prefered VM, how can we export two
> sets of symlinks for that system?

True.

> 
> Of course you can argue that this is an unlikely situation, but what if
> root stops the merge with a ctrl-C? Then the /usr/include/jni.h will be
> completely wrong, in this scheme.
> 

That is is out of the question then.

> 
> As you pointed out yourself, some packages try to be smart and find the
> jni.h themselves. If they use something like if [ -x ${path}/jni.h ],
> putting an -I in CFLAGS won't help much, and the configure script will
> probably stop with an error.
> 

This is one the issues to discuss at DevJam. Standards are a good thing.
Well you could ensure that -I is the first option to the compiler but I
agree that it we should come up with something more bullet proof.

>
> If the package tries to find the jni.h by compiling with various -I
> options, we may get lucky. The only remaining problem then is ensuring
> that we in fact do _not_ have a gcj-installed jni.h in /usr/include,
> since that may take precedence.
>

Let's mail upstream and see what happens.

> 
> 
> -- Karl T

Regards,
Petteri Räty
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDBXfccxLzpIGCsLQRAgYPAJ9tZp7ftQmlU5mRQZTU62BOKEkBEwCghUZU
SIgy+kgCrK5cl6fGJAVCHe0=
=qpms
-----END PGP SIGNATURE-----
-- 
gentoo-java@g.o mailing list