Problem with sunrpc when building GLIBC-2.1
John T. Stapleton
jstapes@gis.net
Wed Mar 17 09:59:00 GMT 1999
I ran into a problem late in the process of building GLIBC-2.1, during
the ``make others'' section. In the sunrpc sub-directory, the
``rpcgen'' program is run using the new ``ld-linux.so.2'' program.
Here is the command broken into separate line to make it easier to
read:
/soft/local/glibc-2.1/elf/ld-linux.so.2 \
--library-path /soft/local/glibc-2.1:/soft/local/glibc-2.1/math: \
/soft/local/glibc-2.1/elf:/soft/local/glibc-2.1/nss: \
/soft/local/glibc-2.1/nis:/soft/local/glibc-2.1/db2: \
/soft/local/glibc-2.1/rt:/soft/local/glibc-2.1/resolv: \
/soft/local/glibc-2.1/linuxthreads \
/soft/local/glibc-2.1/sunrpc/rpcgen \
-Y `gcc -print-file-name=cpp | sed "s|/cpp$||"` \
-c rpcsvc/bootparam.x \
-o /soft/local/glibc-2.1/sunrpc/xbootparam.T
This is the error message that I received:
waitpid: Operation not permitted
This is on a Redhat Linux Alpha System, distribution version 5.1
running kernel version 2.0.34. I did configure GLIBC to use the
headers from version 2.2.3 of the kernel. Here is the configure
command that I used.
../../src/glibc-2.1/configure --prefix=/usr/glibc-2.1 \
--host=alpha-linux --with-headers=/usr/src/linux-2.2.3/include \
--enable-add-ons
If I run the ``rpcgen'' which came with the Redhat distribution, it
works. I spent some time looking in various documentation and FAQ
files, but I could not find anything related to this problem.
The version of the compiler, and the tools that I built along with
the compiler are:
compiler: egcs-2.91.60 19981201 (egcs-1.1.1 release)
binutils: binutils-2.9.1.0.22b
bison: bison-1.27 [see note]
flex: flex-2.5.4a
Note: The bison distribution was built separately before building the
EGCS 1.1.1 release because I had a problem when I made it part of the
EGCS directory tree. If it is part of the EGCS directory tree, then
the EGCS main Makefile defines YACC as
$OBJ/egcs-1.1.1/bison/bison -y -L $SRC/egcs-1.1.1/bison/
and then bison complains when trying to build flex.
Can anyone help?
John
More information about the Gcc-bugs
mailing list