| Summary: | dev-java/java-gnome-4.0.7 compile failure with distcc | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Colin Macdonald <cbm> |
| Component: | [OLD] Java | Assignee: | Java team <java> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | andrew |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Colin Macdonald
2008-05-31 00:26:45 UTC
Huh. I guess the presence of GCJ is screwing things up, but I thought we'd purged all references to that. Weird. I'll have a glance and see if I can figure it out later this week. It shouldn't be too hard to figure out the patch to make it work so you can do a -r1, but since we don't use GCJ or have it installed, this is Works For Me™ otherwise and not something I can actually test. AfC Sydney So what does $ `which gij` -version output on your machine? As for why that is screwing up the C compiler detection, I'm not really sure. AfC Hmmm looks like gij is some old crud in /usr/bin/ on my systems (from 2004ish gcc-config looks like). I'm cleaning it up, then I'll try java-gnome again but this is looking like a local problem. Will report back later. Ok, last comment was not the problem (although it was unrelated mess ;-)
The issue seems to be that the configure script gets confused by distcc. If I stop using distcc (from /etc/make.conf), I get further in the build process.
So the first thing is the configure script doesn't work with distcc. In retrospect this is not surprising given this:
# Workaround ccache needing to be symlinked as gcc
# to perform _as_ gcc. Gentoo bug #180353
if (basename($gcc_candidate) eq "ccache") {
$gcc_candidate = `which gcc`;
}
Its still not building but I'll file another bug to keep one issue per bug.
this version is not in tree anymore. if the problem still persists with current versions, please reopen. |