Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 165494
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Genkernel Maintainers <genkernel@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Tobias Scherbaum <dertobi123@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 165494 depends on: Show dependency tree
Bug 165494 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-02-05 20:26 0000
* ERROR: Could not read /usr/share/genkernel/parisc64/config.sh

The file exists and manually sourcing that file just works (tm).

------- Comment #1 From Chris Gianelloni (RETIRED) 2007-02-12 20:13:40 0000 -------
Are you getting this when running via catalyst?  If so, which version of
catalyst are you using?

------- Comment #2 From Tobias Scherbaum 2007-02-12 20:57:44 0000 -------
(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

------- Comment #3 From Tobias Scherbaum 2007-02-12 21:33:46 0000 -------
Funny thing, it's working again with catalyst 2.0.2. I'll confirm this on
another box tomorrow.

------- Comment #4 From Chris Gianelloni (RETIRED) 2007-02-14 03:55:03 0000 -------
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

------- Comment #5 From Andrew Gaffney 2007-02-14 20:56:43 0000 -------
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.

------- Comment #6 From Chris Gianelloni (RETIRED) 2007-02-14 21:20:27 0000 -------
OK.  This is fixed in subversion now, thanks to Andrew.

------- Comment #7 From Chris Gianelloni (RETIRED) 2007-02-14 21:59:09 0000 -------
Fixed in 3.4.7_pre3

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug