From: Uwe Zeisberger <zeisberg@informatik.uni-freiburg.de>
To: git@vger.kernel.org
Subject: Solaris 8
Date: Mon, 26 Jun 2006 10:09:12 +0200 [thread overview]
Message-ID: <20060626080912.GA3646@informatik.uni-freiburg.de> (raw)
Hello,
when trying to get git running on Solaris 8 (gcc 2.95), there are
several pit-falls:
1) for me, install and tar are GNUish, ginstall and gtar don't exist.
(INSTALL = ginstall, TAR = gtar for SunOS in Makefile)
2) connect.c and merge-index.c use signal() without including signal.h
3) Solaris ships zlib 1.1.3. That version doesn't define
ZLIB_VERNUM. But no, that's not my problem, ... I have it: There is
another zlib version in /usr/local. That's 1.2.3, defining
ZLIB_VERNUM as 0x1230. The compiler uses include files from
/usr/local, but lib from /usr/lib. Aargh, I have to dig the admins
here...
4) libc don't know printf z and t modifier:
alloc.c: In function `alloc_report':
alloc.c:47: warning: unknown conversion type character `z' in format
alloc.c:47: warning: too many arguments for format
alloc.c:48: warning: unknown conversion type character `z' in format
alloc.c:48: warning: too many arguments for format
alloc.c:49: warning: unknown conversion type character `z' in format
alloc.c:49: warning: too many arguments for format
alloc.c:50: warning: unknown conversion type character `z' in format
alloc.c:50: warning: too many arguments for format
mktag.c: In function `verify_tag':
mktag.c:69: warning: unknown conversion type character `t' in format
mktag.c:69: warning: too many arguments for format
mktag.c:72: warning: unknown conversion type character `t' in format
mktag.c:72: warning: too many arguments for format
mktag.c:77: warning: unknown conversion type character `t' in format
mktag.c:77: warning: too many arguments for format
mktag.c:97: warning: unknown conversion type character `t' in format
mktag.c:97: warning: too many arguments for format
mktag.c:104: warning: unknown conversion type character `t' in format
mktag.c:104: warning: too many arguments for format
5) I don't understand why I get this warning for EMIT(c), but not for
EMIT('\\'):
quote.c:34: warning: value computed is not used
quote.c:37: warning: value computed is not used
6) typedef long pid_t
upload-pack.c: In function `create_pack_file':
upload-pack.c:277: warning: int format, pid_t arg (arg 2)
daemon.c: In function `remove_child':
daemon.c:371: warning: int format, pid_t arg (arg 2)
daemon.c: In function `child_handler':
daemon.c:481: warning: int format, pid_t arg (arg 3)
7) I think these can safely be ignored:
builtin-help.c: In function `cmd_help':
builtin-help.c:234: warning: null format string
builtin-help.c:236: warning: null format string
git.c: In function `main':
git.c:280: warning: null format string
I'll send out patches in reply to this mail for 2) and 6)
--
Uwe Zeisberger
main(){char*a="main(){char*a=%c%s%c;printf(a,34,a,34%c";printf(a,34,a,34
,10);a=",10);a=%c%s%c;printf(a,34,a,34,10);}%c";printf(a,34,a,34,10);}
next reply other threads:[~2006-06-26 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 8:09 Uwe Zeisberger [this message]
2006-06-26 8:23 ` [PATCH] include signal.h for prototype of signal() Uwe Zeisberger
2006-06-26 8:51 ` Uwe Zeisberger
2006-06-26 8:26 ` [PATCH] cast pid_t to long for printing Uwe Zeisberger
2006-06-26 9:26 ` Junio C Hamano
2006-06-26 12:13 ` Uwe Zeisberger
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=20060626080912.GA3646@informatik.uni-freiburg.de \
--to=zeisberg@informatik.uni-freiburg.de \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).