From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Jeff Sickel <jas@corpus-callosum.com>
In-Reply-To: <CAG3N4d_2BdmZOz-VYMJ03pUxJN6bFFz0mG2ZiqbD7CQYAs-ZGw@mail.gmail.com>
Date: Mon,  4 Feb 2013 10:11:00 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <20AA79D9-1D4A-41CE-9B34-11B8DBB0747F@corpus-callosum.com>
References: <CAG3N4d9_2kgQGjD0e775=DoMpkRepMvAsA7SOPue1DDn9S3u6w@mail.gmail.com>
	<CAG3N4d_2BdmZOz-VYMJ03pUxJN6bFFz0mG2ZiqbD7CQYAs-ZGw@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] APE libsec
Topicbox-Message-UUID: 14c0a1a8-ead8-11e9-9d60-3106f5b1d025

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:
>=20
> /n/sources/plan9/sys/include/ape/mp.h:5,12 - =
/sys/include/ape/mp.h:5,12
>   #ifndef __LIBMP_H_
>   #define __LIBMP_H_
>  =20
> - #pragma	src	"/sys/src/libmp"
> - #pragma	lib	"libmp.a"
> + #pragma	src	"/sys/src/ape/lib/mp"
> + #pragma	lib	"/$M/lib/ape/libmp.a"
>  =20
>   typedef unsigned int	mpdigit;	/* from =
/$objtype/include/u.h */