Summary: | genkernel fails while sourcing $ARCH_CONFIG | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tobias Scherbaum (RETIRED) <dertobi123> |
Component: | [OLD] Development | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | hppa |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tobias Scherbaum (RETIRED)
2007-02-05 20:26:29 UTC
Are you getting this when running via catalyst? If so, which version of catalyst are you using? (In reply to comment #1) > Are you getting this when running via catalyst? Yep. > If so, which version of catalyst are you using? catalyst 2.0.1, genkernel 3.4.6 Funny thing, it's working again with catalyst 2.0.2. I'll confirm this on another box tomorrow. Can you be sure this is still working with genkernel/catalyst from my overlay? http://overlays.gentoo.org/svn/dev/wolf31o2 (or layman -a wolf31o2) catalyst-2.0.3_pre2 genkernel-3.4.7_pre2 Thanks I've found the cause of this problem. In `genkernel`, the config.sh is used like so: source ${ARCH_CONFIG} || gen_die "Could not read ${ARCH_CONFIG}" This appears to be flawed because `source` doesn't seem to return an exit code. Instead, the exit code of the last command that ran is used. In parisc{,64}/config.sh, that last command was: [ -z "${MAKEOPTS}" ] && MAKEOPTS="-j2" If you have MAKEOPTS exported via a catalyst envscript, the last command to run is `test -z "${MAKEOPTS}"`, which exits with 1, since $MAKEOPTS is not empty. Moving this line near the top of the file like it is in most of the other arch-specific config.sh files does the trick. OK. This is fixed in subversion now, thanks to Andrew. Fixed in 3.4.7_pre3 |