From: Arnd Bergmann <arnd@bergmann-dalldorf.de>
To: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: klibc development release
Date: Fri, 09 Aug 2002 13:33:53 +0200 [thread overview]
Message-ID: <200208090934.g799YVZe116824@d12relay01.de.ibm.com> (raw)
In-Reply-To: <aivdi8$r2i$1@cesium.transmeta.com>
H. Peter Anvin wrote:
> I would particularly appreciate portability comments, since I'm flying
> blind on non-i386 machines (anyone want to send me hardware?),
> although any bug reports would be appreciated.
I just tried compiling for 64 bit s390x, this is what I found so far:
- in include/stdint.h, the definitions for *int_fast*_t conflict with
the 64 bit ones
- mmap.c does not compile because _syscall6 is defined only for i386,
alpha, cris, mips(64) and parisc but not for the other ten architectures.
- syscalls/time.o does not compile because __NR_time is not defined for
alpha, ia64 and s390x
- making klibc cross compilable with 'make CROSS_COMPILE=prefix-' would be
a nice and trivial addition
- compile time warnings: see below
more later when I actually manage to run something
Arnd <><
testvsnp.c: In function `main':
testvsnp.c:14: warning: int format, different type arg (arg 3)
testvsnp.c:17: warning: int format, different type arg (arg 3)
testvsnp.c:20: warning: int format, different type arg (arg 3)
testvsnp.c:23: warning: int format, different type arg (arg 3)
testvsnp.c:31: warning: int format, different type arg (arg 3)
testvsnp.c:36: warning: int format, different type arg (arg 3)
testvsnp.c:39: warning: int format, different type arg (arg 3)
testvsnp.c:42: warning: int format, different type arg (arg 3)
testvsnp.c:45: warning: int format, different type arg (arg 3)
testvsnp.c:48: warning: int format, different type arg (arg 3)
testvsnp.c:51: warning: int format, different type arg (arg 3)
testvsnp.c:54: warning: int format, different type arg (arg 3)
testvsnp.c:57: warning: int format, different type arg (arg 3)
testvsnp.c:60: warning: int format, different type arg (arg 3)
testvsnp.c:63: warning: int format, different type arg (arg 3)
testvsnp.c:66: warning: int format, different type arg (arg 3)
testvsnp.c:69: warning: int format, different type arg (arg 3)
testvsnp.c:72: warning: int format, different type arg (arg 3)
testvsnp.c:75: warning: int format, different type arg (arg 3)
testvsnp.c:79: warning: int format, different type arg (arg 3)
testvsnp.c:83: warning: int format, different type arg (arg 3)
testvsnp.c:87: warning: int format, different type arg (arg 3)
testvsnp.c:90: warning: int format, different type arg (arg 3)
testvsnp.c:93: warning: int format, different type arg (arg 3)
testvsnp.c:96: warning: int format, different type arg (arg 3)
testvsnp.c:99: warning: int format, different type arg (arg 3)
testvsnp.c:102: warning: int format, different type arg (arg 3)
testvsnp.c:105: warning: int format, different type arg (arg 3)
testvsnp.c:108: warning: int format, different type arg (arg 3)
testvsnp.c:111: warning: int format, different type arg (arg 3)
vfprintf.c: In function `vfprintf':
vfprintf.c:26: warning: cast from pointer to integer of different size
fputs.c: In function `fputs':
fputs.c:15: warning: cast from pointer to integer of different size
calloc.c: In function `calloc':
calloc.c:16: warning: type mismatch in implicit declaration for built-in function `memset'
vfprintf.c: In function `vfprintf':
vfprintf.c:26: warning: cast from pointer to integer of different size
fputs.c: In function `fputs':
fputs.c:15: warning: cast from pointer to integer of different size
calloc.c: In function `calloc':
next prev parent reply other threads:[~2002-08-09 9:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 3:39 H. Peter Anvin
2002-08-09 10:14 ` Andreas Schwab
2002-08-09 18:22 ` H. Peter Anvin
2002-08-09 11:33 ` Arnd Bergmann [this message]
2002-08-09 19:53 ` Arnd Bergmann
2002-08-09 18:55 ` H. Peter Anvin
2002-08-09 19:04 ` David Mosberger
2002-08-09 19:14 ` H. Peter Anvin
2002-08-09 22:27 ` Matti Aarnio
2002-08-09 22:37 ` H. Peter Anvin
2002-08-10 6:22 ` Erik Andersen
2002-08-10 6:24 ` H. Peter Anvin
2002-08-10 10:40 ` Christoph Hellwig
2002-08-10 10:48 ` H. Peter Anvin
2002-08-10 10:51 ` Christoph Hellwig
2002-08-10 10:52 ` H. Peter Anvin
2002-08-10 6:21 ` Erik Andersen
2002-08-09 19:55 ` H. Peter Anvin
2002-08-09 20:22 ` David Mosberger
2002-08-09 20:29 ` H. Peter Anvin
2002-08-09 20:16 ` Albert D. Cahalan
2002-08-09 20:22 ` H. Peter Anvin
2002-08-11 5:02 ` Rob Landley
2002-08-11 13:13 ` Alexander Viro
2002-08-12 2:29 ` Oliver Xymoron
2002-08-12 4:39 ` Alexander Viro
2002-08-09 22:03 ` Oliver Xymoron
2002-08-11 5:11 ` Rob Landley
2002-08-11 15:56 ` Oliver Xymoron
2002-08-11 18:20 ` Albert D. Cahalan
2002-08-11 15:31 ` Rob Landley
2002-08-11 21:04 ` Erik Andersen
2002-08-11 22:18 ` H. Peter Anvin
2002-08-12 3:17 ` Jamie Lokier
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=200208090934.g799YVZe116824@d12relay01.de.ibm.com \
--to=arnd@bergmann-dalldorf.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®