Operating System - HP-UX
1833997 Members
2564 Online
110063 Solutions
New Discussion

Re: mk_kernel fails after installing QPK

 
ShanA_2
Occasional Advisor

mk_kernel fails after installing QPK

Hi
i did a fresh install of Hp-ux 11i and installed the QPK patches, but after server reboot i changed the kernel parameter and trying to rebuild the kernel it fails with the below errors

uxd13:/var/sam/log# mk_kernel
Generating module: krm...
Compiling /stand/build/conf.c...
Loading the kernel...
/usr/ccs/bin/ld: (Warning) Ignoring +nodefaultmap. The option is currently not supported in a 32-bit PA link.
/usr/ccs/bin/ld: Unrecognized argument: +Accept
/usr/ccs/bin/ld: Usage: /usr/ccs/bin/ld [options] [flags] files
*** Error exit code 1

Stop.
config: make did an exit(1)

plese help gurus...

regards
Shan
3 REPLIES 3
Mridul Shrivastava
Honored Contributor

Re: mk_kernel fails after installing QPK

There are several reasons that this error will be displayed.

1) /usr/ccs/bin/ar is an empty file .
Recover that file.

2) Having a mix of 32-bit and 64-bit filesets.
Use the command :
# swlist -l fileset -a architecture -a patch_state -a state

The architecture attributes for a 64-bit system must look like :
HP-UX_B.11.00_32/64 or
HP-UX_B.11.11_64
For a 32-bit system the architecture attributes would be :
HP-UX_B.11.00_32/64 or
HP-UX_B.11.11_32

Products that do not match this should be removed from the system.

The patch_state attribute should be committed.

The state attribute should be configured, anything else should be corrected.

3) If (2) above does not report any incorrectly installed software, try to start the mk_kernel with a new clean build
directory :
# mkdir /stand/build.new
# cd /stand/build.new
# cp /stand/system system
# mk_kernel -v -s system


4) Check patch validity with the check_patches command :
# check_patches

This will log information to /tmp/check_patches.report .

Check that report for errors.

5) Is there enough space in the file systems?
# bdf

Especially look at /stand , /tmp, and /var .
If there is not, remove or move some files to create more available space.

For more information see mk_kernel(1m).
Time has a wonderful way of weeding out the trivial
Steven E. Protter
Exalted Contributor

Re: mk_kernel fails after installing QPK

Shalom,

If you did a fresh install of 11.11(11i v1) from December 2006 release there is no reason to install follow up patches, which for this release are called Gold Patch bundles.

If you force installed a QPK which is a designation for 11.00 or 11.23 then this may explain the problem.

Get the December 2006 Core OS media, re-install this.

Then install the HWE, hardware enablement patch and the bundle from the patch center at http://itrc.hp.com

Note that if you used the term QPK in error, you may wish to try your kernel change with sam to make sure you didn't violate limits or forumulas.

I suspect there is information missing at this time that would be helpful in resolving this issue.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Dennis Handly
Acclaimed Contributor

Re: mk_kernel fails after installing QPK

>install of HP-UX 11i

This meaningless, there are 3 versions of this for PA. Which OS version?

>/usr/ccs/bin/ld: Unrecognized argument: +Accept

I have no idea why mk_kernel would ever use an option that was made for gcc.

You need to install the latest linker patch.

>Mridul: /usr/ccs/bin/ar is an empty file

Why are you pointing at this file, since it was ld that gave the error?

>Mridul: Products that do not match this should be removed from the system.

You need to be careful here. It is ok to have 64bit shlibs on a 32 bit system if you are doing development. (You can't test though.)

>SEP: If you did a fresh install of 11.11(11i v1) from December 2006 release there is no reason to install follow up patches, which for this release are called Gold Patch bundles.

You are unfortunately confused. I don't think the linker has ever made it on a Gold or Quality patches. But I can't see why anyone would make a mk_kernel dependent on a patch if it won't be there??

>SEP: If you force installed a QPK which is a designation for 11.00 or 11.23 then this may explain the problem.

Yes, that would confuse things.