From: Eiki Ito <eiki@hal.com>
To: ultralinux@vger.kernel.org
Subject: compiling libc5 on UP1.0
Date: Sun, 10 May 1998 02:20:38 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222356530996@msgid-missing> (raw)
Hi all,
I joined this mailing list recently. Could someone give me an advice
on how to compile libc? I'm using Ultrapenguin-1.0 (not 1.0.9).
Eventually I'll move on to 1.0.9, but for now I have to use 1.0
for a while. And I have to *compile* it, not just use precompiled one.
o I'm using libc-5.3.12-19.src.rpm found in ultrapenguin-1.0/updates/SRPMS.
Is this the right package?
o include/asm should point to asm-sparc64, not asm-sparc, correct?
o If I do 'configure' on UP1.0, it says
"Build sparc-linux library for sparc64 running linux"
I don't need to change sparc64 to sparc, do I?
o (**** this is the main question ****)
Okay, now, when I do 'make depend' (on UP1.0), I get this:
making depend in sparc64
make: Entering an unknown directory
make: *** sparc64: No such file or directory. Stop.
make: Leaving an unknown directory
make[2]: *** [depend] Error 2
make[2]: Leaving directory `/home/eiki/src/libc-5.3.12-19/libc/sysdeps/linux'
It seems we need sysdeps/linux/sparc64. Where is it? sparc/ does not
seem to be an alternative because it needs such things as <psr.h>.
o I boldly went on to 'make' after the failing 'make depend':) Then this:
getgrgid.c:37: conflicting types for `getgrgid'
.../../include/grp.h:78: previous declaration of `getgrgid'
.../../include/linux/socket.h:89: warning: `cmsg_nxthdr' defined but not used
make[1]: *** [../elfstatic/libc/getgrgid.o] Error 1
make[1]: Leaving directory `/home/eiki/src/libc-5.3.12-19/libc/grp'
make: *** [lib] Error 2
I dunno, apparently I'm missing an important patch or something.
o Oh, BTW, I could compile /sbin/init (statically) on redhat4.2, but
this one is not useable on UP1.0, is it? I tried it, but after
execve("/sbin/init",..) in init() (in init/main.c) it was stuck.
Looks like argv/envp was not correctly passed to the user process.
####
Now I'm totally confused with this 32 vs 64 bit stuff... Is it any
better on 1.0.9?
What I'm trying to do is to port Ultrapenguin to another V9 processor,
our SPARC64-III. Architecture differences with Ultra should be minimal,
but this is much harder than I thought...
Thanks,
-------------------------------------
Eiki Ito
HAL Computer Systems, Inc.
1315 Dell Avenue, Campbell, CA95008, USA
e-mail: eiki@hal.com
next reply other threads:[~1998-05-10 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-10 2:20 Eiki Ito [this message]
1998-05-10 2:27 ` compiling libc5 on UP1.0 David S. Miller
1998-05-10 3:57 ` Eiki Ito
1998-05-10 4:10 ` David S. Miller
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-ultrasparc-90222356530996@msgid-missing \
--to=eiki@hal.com \
--cc=ultralinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.