Bug 616446 - 'make cscope' fails in current tree (-50.el6)
'make cscope' fails in current tree (-50.el6)
Status: CLOSED WORKSFORME
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.0
All Linux
low Severity high
: rc
: ---
Assigned To: Aristeu Rozanski
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-20 09:46 EDT by Prarit Bhargava
Modified: 2010-07-20 09:47 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-20 09:47:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Prarit Bhargava 2010-07-20 09:46:24 EDT
Description of problem:

'make cscope' fails.

Version-Release number of selected component (if applicable): 2.6.32-50.el6


How reproducible: 100%


Steps to Reproduce:
1. checkout tree
2. make cscope

  
Actual results:

[root@intel-mccreary-01 rhel6]# make cscope
make: gcc: Command not found
TEST is "None". Update '/home/rhel6/tests' to change.
BUILDID is ".test". Update '/home/rhel6/localversion' to change.
echo "Creating a new module signing key...";
Creating a new module signing key...
gpg: WARNING: unsafe permissions on homedir `.'
gpg: WARNING: unsafe permissions on homedir `.'
gpg: key CD09BEDA: public key "Red Hat Enterprise Linux Driver Update Program <secalert@redhat.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: WARNING: unsafe permissions on homedir `.'
/bin/sh: line 8: gcc: command not found
/bin/sh: line 9: scripts/bin2c: No such file or directory
make[1]: *** [rh-key] Error 127
make: *** [rhkey] Error 2
[root@intel-mccreary-01 rhel6]# 

Expected results: make cscope works.


Additional info: 100% reproducible.
Comment 1 Prarit Bhargava 2010-07-20 09:47:36 EDT
<sigh>

My eyesight is going.

P.

Note You need to log in before you can comment on or make changes to this bug.