From: Alan Au <alanau@cse.unsw.EDU.AU>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] building glibc
Date: Thu, 17 Aug 2000 01:56:35 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205341@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205334@msgid-missing>
On Wed, 16 Aug 2000, H . J . Lu wrote:
> Your kernel header files are too old.
Thanks. You were right.
It gets a bit furthur now but gets the following error:
make[2]: Entering directory `/home/alanau/src/glibc/glibc-2.1-hjl/sunrpc'
/home/alanau/glibc-build/elf/ld-linux.so.2 --library-path
/home/alanau/glibc-build:/home/alanau/glibc-build/math:/home/alanau/glibc-build/elf:/home/alanau/glibc-build/nss:/home/alanau/glibc-build/nis:/home/alanau/glibc-build/db2:/home/alanau/glibc-build/rt:/home/alanau/glibc-build/resolv
/home/alanau/glibc-build/sunrpc/rpcgen -Y `gcc -print-file-name=cpp | sed
"s|/cpp$||"` -c rpcsvc/bootparam_prot.x -o
/home/alanau/glibc-build/sunrpc/xbootparam_prot.T
doSyscall: unimplemented system call 1212
/home/alanau/glibc-build/sunrpc/rpcgen: error in loading shared
libraries: /home/alanau/glibc-build/sunrpc/rpcgen: cannot stat shared
object: Error 38
make[2]: *** [/home/alanau/glibc-build/sunrpc/xbootparam_prot.stmp] Error
127
In fact, get the same error if I invoke the newly built ld.so directly:
bash$ pwd
/home/alanau/glibc-build/elf
bash$ ./ld.so ~/tmp/a.out
doSyscall: unimplemented system call 1212
/home/alanau/tmp/a.out: error in loading shared
libraries: /home/alanau/tmp/a.out: cannot stat shared object: Error 38
Not sure if this is an NUE problem.
Thanks.
Alan
__________
alanau@cse.unsw.edu.au
School of Computer Science and Engineering
University of New South Wales
next prev parent reply other threads:[~2000-08-17 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-16 7:54 [Linux-ia64] building glibc Alan Au
2000-08-16 18:08 ` H . J . Lu
2000-08-17 1:56 ` Alan Au [this message]
2000-08-17 7:26 ` Uros Prestor
2000-08-17 18:34 ` David Mosberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590678205341@msgid-missing \
--to=alanau@cse.unsw.edu.au \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox