Summary: | Compiling kdebase-3.3.2 fails with parse error - maybe related to autoconf/automake | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | enkil <enkil> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
enkil
2004-12-12 13:46:56 UTC
It seems that when bash executes the configure script it fails on basic things like: eval `echo variable=value` and then the compile errors are just a consequence of this. I can't really imagine the reason for such a strange behaviour. Please try again emerging kdebase (you just have to look at the configure output to know if it will fail or not). If it fails, maybe you can try to recompile bash? I recompiled portage, bash, python, baselayout and sed without having effect on portage's configure. I only get configure-errors when using emerge, so I kind of thought portage might somehow cause this. I'll switch to a system-backup without nptl/ntplonly and report if it works with that. I've traced the problem. It was grc. I used grc with portage, that's why a manual ./configure worked. I removed grc-stuff in /etc/portage/bashrc and now configure does work normal. I'm sorry, I should have thought of that one first. I'm somehow new to bugzilla. Should I change the summary to "grc breaks configure in kdebase" and move it to another section, or close it? I guess it should be closed, as there's nothing that could be done about that. Maybe grc should be used as a wrapper to emerge instead of putting it in bashrc? I changed the bug's status to CANTFIX, I hope this is okay. |