Summary: | dev-java/gjdoc-0.7.7-r1 cannot be compiled | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nils Kneuper <crazy-ivanovic> |
Component: | [OLD] Unspecified | Assignee: | Java team <java> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | toolchain |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nils Kneuper
2006-11-02 15:45:31 UTC
Please, re-run gcc-config to set your current stable version and try again (you had eselect-compiler installed at some point?) I did not have eselect-compiler in my system. I only have only one version of gcc installed for a long time already. When migrating to gcc4 I did just follow the migration guide and afterwards I did completely remove the old gcc3 stuff. As prove, here is the output of gcc-config: gcc-config --list-profiles [1] i686-pc-linux-gnu-4.1.1 * The error when doing an emerge -1 gjdoc is still the same. I did now try a workaround by setting the useflag -java for libidn and recompiling this package. This does remove the dependency on gjdoc. Though it would be nice to know why gjdoc does not build on my system (and the amd64 system of my friend). I didn't mean to run --list-profiles, I meant you should run gcc-config 1 and see if it creates the needed symlinks. If not, then reopen this bug. Still the same problem. gcc-config 1 * Switching native-compiler to i686-pc-linux-gnu-4.1.1 ... [ ok ] No new symlinks created, nothing. > > > I hope you either know a way to get rid of that package or a "real" fix for the > problem. > I am quite sure that you are affected by bug 135688. Just do which fastjar and then qfile on that. If it does not belong to any package just remove the file and you should be able to compile gjdoc just fine. If that is not the case, just reopen this bug. *** This bug has been marked as a duplicate of 135688 *** |