Unable to start up ypbind on 1.2.13 kernel

Unable to start up ypbind on 1.2.13 kernel

Post by Henry Ch » Thu, 09 May 1996 04:00:00



I am unable to start up ypbind on 1.2.13 kernel.  I keep getting signal
17 each time I start it andd get a core dump.  Any idea?
--

Henry Y. Cho            
Motorola

                        \\\|||||///
                         = O   O =  
-----------------------o00--( )--00o-----------------------


voice:  (852) 2599-2812
        (852) 2731-6711
fax:    (852) 2724-8578
mobile: (852) 9099-6702

 
 
 

1. Unable to compile a custom 1.2.13 kernel - contains a captured file - help!

I originally (and successfully) installed the base Linux system as described by the
install HOW-TO which supposedly tells me that I am using Linux kernel 1.2.13.

I am trying to re-compile a custom kernel....but with no success.  The directions
say that I should find the new image in /usr/src/linux/arch/boot directory
named as zImage (since I did use the make zImage command)- though no such
file exists when I search for it.  After running the preliminary make
commands...the make clean, depend, etc., I then ran make zImage yielding
"make: error.." messages.

I am relatively sure that I have browsed the pertinent HOWTO FAQs..however,
with no avail.  I have tried to install the "make-3.74(?)", "binutils",
"gcc-2.7.2(?)" and several other packages thinking that some file(s) were
originally missing...but apparently with no success.  (needless to say,
compiling the make utilities also fails with similar "make: error.." messages.

Is there a specific sequence of events to successfully follow for proper
re-compilation of the kernel?  Is it possible that my paths have been
incorrectly configured...hence being able to locate the appropriate
directories/files?  Am i missing other critical utility packages needed to
successfully compile a custom kernel?     H E L P !!!!!

Can someone help me with this issue?  I apologize for not being able to
provide more detailed information...but if there is a patient person
who can help me work this out it will be greatly appreciated.

The following is the output captured via a script I wrote which actually
captures stdout...and stderr only on the "make zImage" command.  You will see
which commands were run in their current order:

.
.
.
running the make zImage now....
gcc -D__KERNEL__ -I/usr/src/linux-1.2.13/include -Wall -Wstrict-prototypes -O2 -fomit-frame-
pointer -pipe -m486  -c -o init/main.o init/main.c
done running the make zImage.
Fri Apr 12 11:56:12 EDT 1996

end of /root/bin/create_zImage.ksh routine

# The following errors appeared after the completion of the script I created to # catch stdout and
stderr on the "make zImage command".  As you can see the name# of my script is
/root/bin/create_zImage.ksh.

io.h:82: inconsistent operand constraints in an `asm'
/usr/src/linux-1.2.13/include/asm/io.h:82: inconsistent operand constraints in an `asm'
/usr/src/linux-1.2.13/include/asm/io.h:82: inconsistent operand constraints in an `asm'
/usr/src/linux-1.2.13/include/asm/io.h:82: inconsistent operand constraints in an `asm'
/usr/src/linux-1.2.13/include/asm/io.h: In function `check_fpu':
/usr/src/linux-1.2.13/include/asm/io.h:78: inconsistent operand constraints in an `asm'
/usr/src/linux-1.2.13/include/asm/io.h:82: inconsistent operand constraints in an `asm'
/usr/src/linux-1.2.13/include/asm/io.h:78: inconsistent operand constraints in an `asm'
/usr/src/linux-1.2.13/include/asm/io.h:82: inconsistent operand constraints in an `asm'
make: *** [init/main.o] Error 1

Your assistance is greatly appreciated!!!!


2. Obtain early versions

3. strange problems 1.2.13 --> 2.0.0 --> 1.2.13

4. Anyone wanna go halves?

5. Unable to build a custom 1.2.13 kernel

6. gcc 2.2.2: stdlib.h/stddef.h wchar_t problem?

7. Can't link kernel 1.2.13: Wrong starting address ?

8. NFS over serial link

9. GCC 2.7.2 unable to compile Linux 1.2.13?

10. 1.2.13 kernel is slower than 1.2.1 kernel

11. IP alias - Kernel crash - 1.2.13 kernel, 3com 3c590 module

12. NCSA httpd 1.3 Won't Start in Linux 1.2.13

13. ypbind ypbind ypbind ypbind ypbind - HELP?