02-07-2008
Kernel Rebuild error
Hi All,
While installing a Service Pack on my Unix Solaris machine, i got the following error:
UX:acomp: ERROR: "space.c", line 16: undefined symbol: CHROOT_SECURITY
UX:acomp: ERROR: "space.c", line 16: non-constant initializer: op "NAME"
UX:idmkunix: ERROR: Compile/link of 'Driver_atup.o space.c' for fs module failed.
Exit code = 256
The UNIX operating system did not build correctly after the update.
After this error the installation aborted. Please advice me on how i can re-build the kernel properly.
Thanks,
Am
10 More Discussions You Might Find Interesting
1. BSD
# cd /usr/src/sys/i386/conf
# cp GENERIC LOVEPP
# cd /usr/src
# make buildkernel KERNCONF=LOVEPP
make:don't know how to make buildkernel. Stop
Any suggestions?
(I am using Freebsd4.8) (2 Replies)
Discussion started by: sheep
2 Replies
2. UNIX for Advanced & Expert Users
Hi All
I am kinda wondering about the UX kernel parameters, how we configure and why do we configure ???.. especially the 'semaphores'. Could somebody throw some light on this and would really appreciate it. (1 Reply)
Discussion started by: Prince_Charming
1 Replies
3. Solaris
When I run the Oracle installer, following checks are failed:
Checking for shmsys:shminfo_shmmax=4294967295; found no entry. Failed <<<<
Checking for shmsys:shminfo_shmmni=100; found no entry. Failed <<<<
Checking for semsys:seminfo_semmni=100; found no entry. Failed <<<<
Checking... (1 Reply)
Discussion started by: aa_monster
1 Replies
4. UNIX for Dummies Questions & Answers
I'm getting the following Error:
prepare_pcap.c: In function `prepare_pkts':
prepare_pcap.c:127: error: dereferencing pointer to incomplete type
prepare_pcap.c:138: error: dereferencing pointer to incomplete type
====================================
This is the part of the relevant... (8 Replies)
Discussion started by: katwala
8 Replies
5. Solaris
I tried to install the kernel patch 118855-36 in my x86 machine which has Solaris 10 installed. Find below the error message....
#patchadd 118855-36
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
118855-36
Executing... (1 Reply)
Discussion started by: paventhan
1 Replies
6. UNIX Benchmarks
Just for fun:
CPU/Speed: 2x AMD Opteron Model 2384 (2.7GHz/512KB) quad core processor
Ram: 4 x2GB ECC DDR2-667 single rank memory
in RAID 0 mode (strip 128KB, Read Caching enabled, Write Caching disabled) with 2 HDD, CPUTYPE=opteron, CFLAGS= -O2 -fno-strict-aliasing -pipe, CXXFLAGS+=... (0 Replies)
Discussion started by: Success_Tree
0 Replies
7. UNIX for Dummies Questions & Answers
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
Discussion started by: h0ujun
0 Replies
8. Linux
Hi,
Can i just ask how I can create a bootable PXE image from the built kernel source.
What files do I need to get?
Thanks! (1 Reply)
Discussion started by: h0ujun
1 Replies
9. Solaris
Not very helpful to say the least. Seems to read the flar file and go through the upgrade and then come up with this error.
Any ideas? (1 Reply)
Discussion started by: psychocandy
1 Replies
10. SuSE
http://uploads.tapatalk-cdn.com/20160725/0174562490859032f68430fb0fa216cd.jpg
I have created a personally made SUSE-based distro using susestudio.com and it will install just fine on my laptops (32-bit Acer Aspire One ZG5 and MacBook 4,1). However, when installing on an old Emachine desktop, I... (6 Replies)
Discussion started by: TheOuterLinux
6 Replies
LEARN ABOUT CENTOS
error::pass4
ERROR::PASS4(7stap) ERROR::PASS4(7stap)
NAME
error::pass4 - systemtap pass-4 errors
DESCRIPTION
Errors that occur during pass 4 (compilation) have generally only a few causes:
kernel or OS version changes
The systemtap runtime and embedded-C fragments in the tapset library are designed to be portable across a wide range of OS versions.
However, incompatibilities can occur when some OS changes occur, such as kernel modifications that change functions, types, or
macros referenced by systemtap. Upstream builds of systemtap are often quickly updated to include relevant fixes, so try getting or
making an updated build. If the issue persists, report the problem to the systemtap developers.
buggy embedded-C code
Embedded-C code in your own guru-mode script cannot be checked by systemtap, and is passed through verbatim to the compiler. Errors
in such snippets of code may be found during the pass-4 compiler invocation, though may be hard to identify by the compiler errors.
incompatible embedded-C code
The interface standards between systemtap-generated code and embedded-C code occasionally change. For example, before version 1.8,
arguments were passed using macros THIS->foo and THIS->__retvalue but from version 1.8 onward, using STAP_ARG_foo and STAP_RETVALUE.
Adjust your embedded-C code to current standards, or use the stap --compatible=VERSION option to make systemtap use a different one.
GATHERING MORE INFORMATION
It may be necessary to run systemtap with -k or -p3 to examine the generated C code. Increasing the verbosity of pass-4 with an option
such as --vp 0001 can also help pinpoint the problem.
SEE ALSO
stap(1),
error::reporting(7stap)
ERROR::PASS4(7stap)