- upstream moved to github, so update HOMEPAGE
- add a patch to pledge the bgpdump tool
diff /usr/ports
commit - 3dc374ed609f6e20415237a3a8941a0f33d03779
path + /usr/ports
blob - 586e6ed7da977759ba67c0cd143140e00fa188b2
file + net/libbgpdump/Makefile
--- net/libbgpdump/Makefile
+++ net/libbgpdum
Hi,
This port can now be fetched as a tagged version instead of a commit; it
looks like upstream started tagging releases in 2020 a few months after
the last time the port was updated.
The existing port sets -DVGA_amd64 to only compile support for
disassembling amd64. Trying to load a binary fo
Hi,
The version of PySMT in ports is broken under Python 3.10 because it
uses imports that were removed in Python 3.8.
See: https://github.com/pysmt/pysmt/pull/562
Updating to the most recent upstream version fixes it.
Tested by using py3-angr, which depends on it.
--- math/py-pysmt/Makefile
Update to 1.4.12, based on the last diff that was sent to the list.
The manpage and mu-str.h patches were both merged upstream in this
release, so they are no longer needed.
Both flavors build and pass tests on amd64 and arm64.
Besides the patches, the only change I made is to use the GUILE_V
va
Todd Carson writes:
> Stuart Henderson writes:
>
>>> +make this function compile correctly under clang
>>> +Index: lib/utils/mu-str.c
>>> +--- lib/utils/mu-str.c.orig
>>> lib/utils/mu-str.c
>>> +@@ -49,7 +49,7 @@ mu_str_size_s
Stuart Henderson writes:
>> +make this function compile correctly under clang
>> +Index: lib/utils/mu-str.c
>> +--- lib/utils/mu-str.c.orig
>> lib/utils/mu-str.c
>> +@@ -49,7 +49,7 @@ mu_str_size_s (size_t s)
>> + char*
>> + mu_str_size (size_t s)
>> + {
>> +- return g_strdup (mu_str_siz
This incorporates the changes previously posted for 1.4.3, with the
exception of the README since there seemed to be some disagreement about
that.
I also added a FLAVOR to optionally build the guile bindings, with some
patches to change hard-coded references to guile and guile-snarf to
guile2.2 a
On Sat, Jun 25, 2011 at 05:56:17PM -0400, James Turner wrote:
> > I'm going to re-compile with --enable-debug. Hopefully this will provide
> > a better backtrace. I'll report back in a couple days when webkit
> > finishes compiling...
> >
>
> When attempting to compile with --enable-debug it seems
On Tue, May 17, 2011 at 08:01:57AM +0200, Otto Moerbeek wrote:
> On Mon, May 16, 2011 at 11:03:58PM +0200, Otto Moerbeek wrote:
>
> > Hi,
> >
> > webkit 1.4.0 allocates 1G of mem from the start on amd64. That's above
> > our default ulimit. This changes the initial allocation to be more
> > modes
This adds two patches.
One fixes a crash at runtime on amd64, sparc64, and possibly other 64-bit
machines.
The other is a fix for a two year-old xterm command injection bug, CVE
2008-2383.
I took the latter from a report on the upstream bug tracker. The project
appears to be dead, so they never co
On Sun, Mar 06, 2011 at 07:57:34AM -0600, Marco Peereboom wrote:
> I can confirm that backing that out fixes the regression.
>
> On Sun, Mar 06, 2011 at 09:28:58AM +0100, Landry Breuil wrote:
> > >
> > > Backing out
> > > http://gitorious.org/webkitgtk/stable/commit/d842bb085aceec4fcfc392a7b76c92
On Tue, Feb 15, 2011 at 09:51:15AM +0100, Landry Breuil wrote:
> And what commit causing crashes on 64-bit are you talking about ?
http://gitorious.org/webkitgtk/stable/commit/f236c158708a2116a799174bd2722fd721e663c4
https://bugs.webkit.org/show_bug.cgi?id=41795
This was the cause of the crash re
On Mon, Feb 07, 2011 at 09:58:58AM +0100, Landry Breuil wrote:
> On Sat, Feb 05, 2011 at 04:36:15PM -0500, Todd Carson wrote:
> > The problem is that they changed some variables from signed to unsigned,
> > which leads to an array subscript calculation coming out wrong on 64-
On Sat, Feb 05, 2011 at 02:40:21PM -0500, Brian Callahan wrote:
> Hello list,
>
> On a -current loongson maching dated Jan 30, I built webkit 1.2.6 from
> ports. The build completes fine, but when trying to access a page containing
> Javascript, webkit crashes the web browser. This behavior happen
14 matches
Mail list logo
