topic kernel compiling error in Operating System - HP-UX

kernel compiling error

Charles Darnell_1 — Wed, 16 Oct 2002 17:51:02 GMT

# mk_kernel -v -s system
Building a new kernel based on template file "system"

Generating Module: krm...
Compiling conf.c...
loading the kernel...

ld: Unsatisfied symbol "mi_cisha1_hmac" in file /usr/conf/lib/libencdom.a[reg_sha1.o]
ld: Unsatisfied symbol "mi_cimd5_hmac" in file /usr/conf/lib/libencdom.a[reg_md5.o]
ld: Unsatisfied symbol "mi_md5_hmac" in file /usr/conf/lib/libencdom.a[reg_md5.o]
ld: Unsatisfied symbol "mi_sha1_hmac" in file /usr/conf/lib/libencdom.a[reg_sha1.o]
4errors. Error exit code 1

Stop.
config: make did an exit(1) config failure.

I have the most recent mk_kernel patches, PHKL_15687 and PHKL_19291. I've tried both in SAM and on command line. In addition, I've tried different systems files. And I tried the windows approach and rebooted. =\ Any suggestions?

Re: kernel compiling error

steven Burgess_2 — Wed, 16 Oct 2002 18:48:30 GMT

Hi Charles

The Unsatisfied symbol kernel build failure occurred because the
/etc/conf/master.d/ipsec-isu file is physically ordered before the
net file in the /usr/conf/master.d directory.

The solution is to change the order in which the libraries are
specified within the ipsec-isu file.

This is an excerpt from the current ipsec_isu file:

117 * Note: libhp-ux.a must be the last entry, do not place anything
after it.
118 *
119 * Library
120 *
121 libauth.a 0 <-- Move this line after line 123 libencdom.a
122 libencint.a 0
123 libencdom.a 0
124 libvvipsec.a 0
125 $$$

Before performing a system backup, modify /usr/conf/master.d/ipsec-isu
in the following manner:

* Note: libhp-ux.a must be the last entry, do not place anything
* after it.
*
* Library
*
libencint.a 0
libencdom.a 0
libvvipsec.a 0
libauth.a 0
$$$

Note that libauth.a has been moved to the last position. The 'key'
to solving the Unsatisfied symbol failure is to make sure libauth.a
is ordered below libencdom.a.

HTH

Steve

Re: kernel compiling error

Charles Darnell_1 — Wed, 16 Oct 2002 20:21:35 GMT

Thanks so much! That was the fix! I had to call HP on that one =P