9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] APE libsec
Date: Mon,  4 Feb 2013 10:11:00 -0600	[thread overview]
Message-ID: <20AA79D9-1D4A-41CE-9B34-11B8DBB0747F@corpus-callosum.com> (raw)
In-Reply-To: <CAG3N4d_2BdmZOz-VYMJ03pUxJN6bFFz0mG2ZiqbD7CQYAs-ZGw@mail.gmail.com>

Whew, the libsec.h file was correct on the first push.

APE builds of libmp and libsec are being rolled in to support a new Python 2.7.3+
port.  Like what you've started doing, the new Python port will not have OpenSSL
linked in and instead uses libsec.

-jas

On Feb 4, 2013, at 5:44 AM, Yaroslav <yarikos@gmail.com> wrote:

> The mp.h fix:
> 
> /n/sources/plan9/sys/include/ape/mp.h:5,12 - /sys/include/ape/mp.h:5,12
>   #ifndef __LIBMP_H_
>   #define __LIBMP_H_
>   
> - #pragma	src	"/sys/src/libmp"
> - #pragma	lib	"libmp.a"
> + #pragma	src	"/sys/src/ape/lib/mp"
> + #pragma	lib	"/$M/lib/ape/libmp.a"
>   
>   typedef unsigned int	mpdigit;	/* from /$objtype/include/u.h */




  reply	other threads:[~2013-02-04 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 11:31 Yaroslav
2013-02-04 11:44 ` Yaroslav
2013-02-04 16:11   ` Jeff Sickel [this message]
2013-02-05  8:32     ` yaroslav
2013-02-05  8:41       ` Jens Staal
2013-02-05 15:28         ` erik quanstrom
2013-02-05 15:38       ` erik quanstrom
2013-02-08 15:35         ` Yaroslav
2013-02-09  2:46           ` Jeff Sickel
2013-02-12 21:27             ` michaelian ennis
2013-02-04 13:06 ` lucio
2013-02-04 15:46   ` erik quanstrom
2013-02-04 15:50     ` lucio

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=20AA79D9-1D4A-41CE-9B34-11B8DBB0747F@corpus-callosum.com \
    --to=jas@corpus-callosum.com \
    --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).