From: John Floren <john@jfloren.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] /ape/libcrypto.a ??none??: /386/lib/ape/libssl.a first
Date: Thu, 19 Jan 2012 11:03:15 -0800 [thread overview]
Message-ID: <CAL4LZyiHkgnR4=7ShqV3aYQUgQ9XY+hw_U8PVhg-74ajv7=Scg@mail.gmail.com> (raw)
In-Reply-To: <ef71e8dc-9b0f-4370-8525-444f7759fae3@k29g2000vbl.googlegroups.com>
On Thu, Jan 19, 2012 at 2:32 AM, ROuNIN <rounin.urashima@googlemail.com> wrote:
> Hello!
> I still get the following:
>
> pcc -o 8.out app_rand.8 apps.8 asn1pars.8 ca.8 ciphers.8 crl.8
> crl2p7.8 dgst.8 dh.8 dhparam.8 dsa.8 dsaparam.8 ec.8 ecparam.8 enc.8
> engine.8 errstr.8 gendh.8 gendsa.8 genrsa.8 nseq.8 ocsp.8 openssl.8
> passwd.8 pkcs12.8 pkcs7.8 pkcs8.8 prime.8 rand.8 req.8 rsa.8 rsautl.8
> s_cb.8 s_client.8 s_server.8 s_socket.8 s_time.8 sess_id.8 smime.8
> speed.8 spkac.8 verify.8 version.8 x509.8 /386/lib/ape/libssl.a /386/
> lib/ape/libcrypto.a
> ar vu /386/lib/ape/libregexp.a regcomp.8 regerror.8 regexec.8 regsub.8
> regaux.8 rregexec.8 rregsub.8
> ar vu /386/lib/ape/libutf.a rune.8 runestrcat.8 runestrchr.8
> runestrcmp.8 runestrcpy.8 runestrdup.8 runestrlen.8 runestrecpy.8
> runestrncat.8 runestrncmp.8 runestrncpy.8 runestrrchr.8 runestrstr.8
> runetype.8 utfecpy.8 utflen.8 utfnlen.8 utfrrune.8 utfrune.8 utfutf.8
> ar vu /386/lib/ape/libv.a getpass.8 tty.8 rand.8 nrand.8 getfields.8
> min.8 max.8 error.8 nap.8
> pcc -c /sys/src/cmd/gs/zlib/gzio.c
> /sys/src/cmd/gs/zlib/gzio.c:181[stdin:1575] function args not checked:
> fdopen
> /sys/src/cmd/gs/zlib/gzio.c:627[stdin:1995] incompatible types: "INT"
> and "VOID" for op "AS"
> pcc: cpp: 8c 9278: error
> mk: pcc -c /sys/src/cmd/gs/zlib/gzio.c : exit status=rc 9275: pcc
> 9277: cpp: 8c 9278: error
> mk: for (i in ... : exit status=rc 5839: rc 9272: mk 9274: error
> mk: cd lib mk all : exit status=rc 5831: mk 5834: error
> mk: mk lib.all mk ... : exit status=rc 5828: mk 5830: error
> mk: date for (i ... : exit status=rc 5075: rc 5825: mk 5827: error
> term%
>
> What do I need to do? Sorry, I may need an extra detailed explanation
> on what to do.
> ROuNIN
>
I just saw this yesterday. Basically, vsnprintf may return an int or
nothing depending on your library (in APE, it depends on whether or
not you've defined _C99_SPRINTF_EXTENSION). By default, APE is going
to give you a vsnprintf that returns void, but the code expects it to
return int. You can get around this by adding -DHAS_vsnprintf_void to
the CFLAGS variable in /sys/src/ape/lib/z/mkfile.
John
next prev parent reply other threads:[~2012-01-19 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 11:15 [9fans] /ape/libcrypto.a ??none??: /386/lib/ape/libssl.a: first ROuNIN
2011-12-23 9:52 ` Steve Simon
2012-01-03 10:49 ` ROuNIN
2012-01-03 17:39 ` Steve Simon
2012-01-03 18:19 ` erik quanstrom
2012-01-03 21:05 ` Lyndon Nerenberg
2012-01-03 21:19 ` erik quanstrom
2012-01-19 10:32 ` [9fans] /ape/libcrypto.a ??none??: /386/lib/ape/libssl.a first ROuNIN
2012-01-19 19:03 ` John Floren [this message]
2012-01-19 19:21 ` Federico G. Benavento
2012-01-03 10:48 ` [9fans] /ape/libcrypto.a ??none??: /386/lib/ape/libssl.a first entry not symbol header too many errors pcc: 8l: 8l 1453: error ROuNIN
2012-01-03 17:40 ` Steve Simon
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='CAL4LZyiHkgnR4=7ShqV3aYQUgQ9XY+hw_U8PVhg-74ajv7=Scg@mail.gmail.com' \
--to=john@jfloren.net \
--cc=9fans@9fans.net \
/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).