non port: lang/scm/files/patch-warnings |
Number of commits found: 4 |
Saturday, 6 Jan 2024
|
21:09 Mikhail Teterin (mi)
lang/scm: stop patching the unused gmalloc.c
Also add a patch from Debian and (what seems like an improvement) from the
upstream's CVS-repository.
f185863 |
Thursday, 4 Jan 2024
|
21:05 Mikhail Teterin (mi)
lang/scm: upgrade from 5f2 to 5f3.
Add TEST_TARGET, fix up licensing information to the best of my
ability to understand it. The software comes with both GPLv3 and
GPLv3-lesser files:
https://directory.fsf.org/wiki/Scm#tab=Details
Picking the less restrictive one.
Prodded by: portscout
dd09d1b |
Sunday, 18 Nov 2018
|
22:06 mi
Try to improve chances of successful build - including, but not
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
|
Tuesday, 27 Jan 2015
|
08:40 mi
Upgrade from 5f1 to 5f2.
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...
|
Number of commits found: 4 |