On Sunday, 20 November 2016 14:28:05 Benjamin wrote:
> Hello,
Hi
> as the pypy build process does no longer detect libressl as unsupported,
> the port should not be ignored with libressl anymore.
>
> I attached a patch removing the check for libressl.
Thank you, it has been committed in r42682
On Tuesday, 15 March 2016 09:43:15 Bartłomiej Rutkowski wrote:
> > On 14 Mar 2016, at 19:47, Konstantin Belousov wrote:
> >
> > Hello,
> > is pypy supposed to build on i386 ? I get the following error on the
> > attempt to build pypy in i386 current jail on current amd64 box.
> >
> > uname -a
>
On Sunday, 13 March 2016 15:36:44 David Naylor wrote:
> Hi,
>
> FYI, I have started on the update to version 5.0.0 for PyPy.
PyPy has been updated to 5.0.0 in r411015.
> Is anyone available to help fix some unit tests?
The unit tests fail to run to completion. The highlights of
Hi,
FYI, I have started on the update to version 5.0.0 for PyPy.
Is anyone available to help fix some unit tests?
Regards,
dbn
signature.asc
Description: This is a digitally signed message part.
On Wednesday, 9 December 2015 18:39:43 Kubilay Kocak wrote:
> On 9/12/2015 6:04 PM, David Naylor wrote:
> > Hi,
> >
> > A comment in a PR recently came up that impacts python@:
> >
> > On Sunday, 22 November 2015 14:44:41 bugzilla-nore...@freebsd.org wrote:
>
Hi,
A comment in a PR recently came up that impacts python@:
On Sunday, 22 November 2015 14:44:41 bugzilla-nore...@freebsd.org wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204743
> Also, given the maintainer's lack of responsiveness, I'd suggest moving pypy
> port maintainer from
, 24 August 2015, 23:07:20
From: David Naylor
To: pypy-...@python.org
CC: Matti Picus
On Saturday, 22 August 2015 21:25:44 Matti Picus wrote:
> I would like to add the freebsd-9-x86-64 binary tgz to our released
> downloads. We still have a number of failing tests showing up on
On Wednesday, 29 July 2015 09:06:40 Konstantin Belousov wrote:
> On Wed, Jul 29, 2015 at 07:46:14AM +0200, David Naylor wrote:
> > On Tuesday, 28 July 2015 22:05:54 Bart??omiej Rutkowski wrote:
> > > I've checked how linux does it and it seems they're (at
On Tuesday, 28 July 2015 22:05:54 Bartłomiej Rutkowski wrote:
> I've checked how linux does it and it seems they're (at least Debian)
doing
> static linking - that would fix the issue, whatever it is. Can you adjust
> the port to do the static instead of dynamic linking binary?
```
# cd /usr/loca
On Tuesday, 28 July 2015 17:08:37 Bryan Drewery wrote:
> On 7/28/15 11:46 AM, David Naylor wrote:
> > Why would the shared library be found when using a relative path
but not
> > when using an absolute path? Is this a bug in FreeBSD?
>
> What is the output for readelf?
&
Hi Hackers,
I am busy simplifying the lang/pypy port (see
https://reviews.freebsd.org/D3209) however I have uncovered a rather
strange problem:
## BACKGROUND ##
PyPy has it's own directory layout so we install it into $PREFIX/pypy-2.6. In
there is everything pypy needs including bin/pypy (the
Hi,
lang/pypy was originally set up to achieve:
* building of multiple pypy instances based on different setting (i.e. with
or without jit, sandboxing, etc). The port user could define any permutation
she desires.
* Install in a directory layout more similar to lang/python (i.e. libraries
On Tuesday, 31 March 2015 20:47:38 Roland Smith wrote:
> On Mon, Mar 30, 2015 at 09:14:40PM +0200, David Naylor wrote:
> > Hi,
> >
> > I am investigating converting my ports to concurrent however I am not sure
> > how concurrent is supposed to work:
> >
>
Hi,
I am investigating converting my ports to concurrent however I am not sure how
concurrent is supposed to work:
I looked in /usr/ports/Mk and only found a documentation reference to
'concurrent'. Setting USE_PYTHON=concurrent doesn't appear to actually change
any behaviour.
Please could
bage collector repeatedly traversing the
entire memory set).
On Tuesday, 10 June 2014 18:12:55 David Naylor wrote:
> Author: dbn
> Date: Tue Jun 10 18:12:55 2014
> New Revision: 357358
> URL: http://svnweb.freebsd.org/changeset/ports/357358
> QAT: https://qat.redports.org/builda
Hi,
The version of pypy in ports is not a standard version, as it tries to follow
the directory layout of python and not have everything in its own
subdirectory.
As a result of this virtualenv support does not work. A large portion of the
problem is that virtualenv hard codes directory path
On Thursday, 1 August 2013 21:50:23 Marcus von Appen wrote:
> On, Thu Aug 01, 2013, David Naylor wrote:
> > Hi All,
> >
> > The pypy team have released a version of pypy that supports python-3.2
> > (while the existing port supports python-2.7).
> >
> >
On Saturday, 3 August 2013 14:58:04 Marcus von Appen wrote:
> On, Sat Aug 03, 2013, David Naylor wrote:
> > On Saturday, 3 August 2013 12:32:45 Marcus von Appen wrote:
> > > Support for non-CPython implementations:
> > >
> > > - A mid-term goal should be to o
On Saturday, 3 August 2013 12:32:45 Marcus von Appen wrote:
> ...at the same time.
>
> Use PKGNAMEPREFIX/SUFFIX for python ports
>
> - this is a clean up task (which should be done regardless of everything
> else). Some python modules miss the prefix, making it impossible to
> install them fo
Hi All,
The pypy team have released a version of pypy that supports python-3.2 (while
the existing port supports python-2.7).
I would like to quickly talk about two concepts here:
* python language version (such as python-2.7, python-3.2, etc)
* python implementation version (such as pypy-2.
On Sunday, 10 March 2013 00:37:15 poyop...@puripuri.plala.or.jp wrote:
> Hi, good work, David.
Hi Kuro
> It compiles, packages and works flawlessly here for replacement of 1.9
> so far for a week.
Great, thanks. Good to know :-)
> On my compile box, amd64/Athlon64 5050e 2.6GHz 2 core/8GB,
> m
Hi All.
After many months of (sporadic) work I would like to introduce pypy-2.0.b1.
Could you please have a look at, and test, my proposed changes (attached) and
the wiki page at http://wiki.FreeBSD.org/PyPy.
I would like to commit these changes (after incorporating feedback) sometime
next
The following reply was made to PR ports/163063; it has been noted by GNATS.
From: David Naylor
To: freebsd-ports-b...@freebsd.org,
bug-follo...@freebsd.org
Cc:
Subject: Re: ports/163063: [PATCH] fix for ports-mgmt/portbuilder
Date: Tue, 24 Apr 2012 21:57:35 +0200
--nextPart1915457
This does not appear to be fixed:
# python --version
Python 2.7.3
# python -c "from select import *; kevent(0, KQ_FILTER_PROC, KQ_EV_ADD |
KQ_EV_ENABLE, KQ_NOTE_EXIT)"
Traceback (most recent call last):
File "", line 1, in
OverflowError: signed integer is greater than maximum
# python32 --vers
Hi All,
As of 2011/12/13 pypy-1.7 is in ports (under lang/pypy, thanks lwhsu@).
Please uninstall pypy-1.6 before building pypy-1.7, there is a memory leak in
pypy-1.6 that prevents it from translating pypy-1.7.
For those that are interested, there is a TODO list [1] and the WIP repository
f
the box. The 1.6
branch targets the upcoming pypy-1.6. To get that to work you need to
checkout the pypy repository (or a nightly snapshot of the code, if it exists)
and then use:
# make install WRKSRC=/path/to/pypy-1.6
On Wednesday, 8 June 2011 21:25:47 David Naylor wrote:
> Hi,
>
&g
Hi,
I have been working on a port for pypy-1.5. Although the port is a work in
progress I would like some feedback for what I have done so far.
The port supports translating (and compiling) multiple instances of pypy, with
three options available by default. The first is DEFAULT which is th
Hi,
I built Python with PTH and SEM. This fixed a problem I had with a python
script I was using to compile ports. See below for a sample script that
triggers a freezes with forked python threads (and something to do with
cmake).
However some KDE ports failed to compile with the 'new' pyth
28 matches
Mail list logo
