MD5 (dangerdeep-0.1.1.tar.gz) = 7de20b4594c0fee8d3c1a281f686f943
SHA256 (dangerdeep-0.1.1.tar.gz) = de6334c88bac6ce1463e48444e550899a61ea85cecf8929a160d07e28f502a20
SIZE (dangerdeep-0.1.1.tar.gz) = 23831169
0:00</updated>
<author>
<name>mi</name>
<email>mi@FreeBSD.org</email>
</author>
<published>2018-11-18T22:06:44+00:00</published>
<link rel='alternate' type='text/html' href='http://tfcis.org/~lantw44/cgit/cgit.cgi/freebsd-ports-gnome/commit/?id=0bff0c75520ee704375b55d4e1d33d852f57dbc5'/>
<id>0bff0c75520ee704375b55d4e1d33d852f57dbc5</id>
<content type='text'>
limited to disabling compiler-optimizations.

Proper fixing seems inherently impossible -- even with -O0 valgrind
flags hundreds of unitilized memory accesses during self-check.

Tested with gcc8 and the base cc (clang) -- remove the GCC-requirement.

Add some patches from Debian.

While here simplify the extract-target a little and remove the BROKEN*
lines to attempt building on other platforms again...

Bump port-revision.

PR:		 232936
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
limited to disabling compiler-optimizations.

Proper fixing seems inherently impossible -- even with -O0 valgrind
flags hundreds of unitilized memory accesses during self-check.

Tested with gcc8 and the base cc (clang) -- remove the GCC-requirement.

Add some patches from Debian.

While here simplify the extract-target a little and remove the BROKEN*
lines to attempt building on other platforms again...

Bump port-revision.

PR:		 232936
</pre>
</div>
</content>
</entry>
<entry>
<title>Stop avoiding the gmalloc-implementation bundled with the code in the hope,</title>
<updated>2015-08-19T16:40:57+00:00</updated>
<author>
<name>mi</name>
<email>mi@FreeBSD.org</email>
</author>
<published>2015-08-19T16:40:57+00:00</published>
<link rel='alternate' type='text/html' href='http://tfcis.org/~lantw44/cgit/cgit.cgi/freebsd-ports-gnome/commit/?id=fa94641cefd325892e0722ee8636289a95ff82cf'/>
<id>fa94641cefd325892e0722ee8636289a95ff82cf</id>
<content type='text'>
it will help get rid of the occasional crashes (reported upstream 6 months
ago to no avail).

Fix plist as reported in:

PR:		202489
Submitted by:	amdmi3
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
it will help get rid of the occasional crashes (reported upstream 6 months
ago to no avail).

Fix plist as reported in:

PR:		202489
Submitted by:	amdmi3
</pre>
</div>
</content>
</entry>
<entry>
<title>Upgrade from 5f1 to 5f2.</title>
<updated>2015-01-27T08:40:34+00:00</updated>
<author>
<name>mi</name>
<email>mi@FreeBSD.org</email>
</author>
<published>2015-01-27T08:40:34+00:00</published>
<link rel='alternate' type='text/html' href='http://tfcis.org/~lantw44/cgit/cgit.cgi/freebsd-ports-gnome/commit/?id=f190b3c1abe6f8257878c76b7b935b00b19821b9'/>
<id>f190b3c1abe6f8257878c76b7b935b00b19821b9</id>
<content type='text'>
The bad news:

	1. gcc is still required -- clang can build the binaries, but
	   some self-tests will fail, unless all optimization was
           disabled. This is, probably, due to some suspect code in
           bytenumb.c -- would be good to investigate.
	2. Building this port in parallel is still not possible -- the
	   Makefile is too convoluted and same sources are recompiled
	   multiple times with different #defines set.

The good news:

	1. Resolve a large number of warnings.
	2. Fix build on ia64 and sparc64 (tested on pluto and flame
           respectively). Other platforms (alpha, powerpc?) have a
	   better chance of working now...
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The bad news:

	1. gcc is still required -- clang can build the binaries, but
	   some self-tests will fail, unless all optimization was
           disabled. This is, probably, due to some suspect code in
           bytenumb.c -- would be good to investigate.
	2. Building this port in parallel is still not possible -- the
	   Makefile is too convoluted and same sources are recompiled
	   multiple times with different #defines set.

The good news:

	1. Resolve a large number of warnings.
	2. Fix build on ia64 and sparc64 (tested on pluto and flame
           respectively). Other platforms (alpha, powerpc?) have a
	   better chance of working now...
</pre>
</div>
</content>
</entry>