I maintain the gclasspath package (formerly classpath), and I recently learned that it has file conflicts with gcc43. For some reason, gcc43 installs classpath along with it, and it does strange things to the files. For instance, it installs the classpath binaries to %p/lib/ gcc4.3/bin, and then it creates symbolic links to a couple of them in %p/bin (grmic and grmiregistry). I don't know why it puts only these two in bin but not others. Even stranger, it installs man pages for a bunch of classpath executables without making those executables available in %p/bin, and it installs only one of the three classpath info files.

I've decided to work around these problems by making classpath dependent on gcc43 and simply preventing it from installing the files that gcc43 installs. It can therefore fill in the gaps left by gcc43. However, I'm not sure if this decision is correct or even if I've implemented it properly. Could someone please take a look at it?

Thanks,

Trevor

Attachment: gclasspath.info
Description: Binary data


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel

Reply via email to