Am 20.07.22 um 17:34 schrieb s...@freebsd.org:
[...]
I'll commit an update to the svgalib port when I succeed in locating the
line that issues the "rm -f" command that deletes those files.
I cn see "unlink" system calls being issued to remove them and I see the
PID of the rm command (or rather s
Am 20.07.22 um 14:55 schrieb Tomoaki AOKI:
[...]
Looking into commit log at cgit [1], the problematic file is already
there at the first commit and unchanged afterwards. So the file should
be there when you installed (or previously updated).
See my reply to the OP, this is a port that removes f
Am 20.07.22 um 14:05 schrieb Andy Farkas:
If I use portmaster to re-build all of my ports it fails at svgalib:
Yes, that port is unmaintained (MAINTAINER=ports@freebsd.org) and
*severely* broken.
I have just spent half an hour trying to identify where the breakage
originates, will look a bit
On Wed, 20 Jul 2022 22:05:19 +1000
Andy Farkas wrote:
>
> If I use portmaster to re-build all of my ports it fails at svgalib:
>
> %%%
> # portmaster -adf
> ...
> gmake[2]: Leaving directory
> '/usr/ports/work/usr/ports/graphics/svgalib/work/svgalib-1.4.3/doc'
>
> Now run 'make demoprogs' to
If I use portmaster to re-build all of my ports it fails at svgalib:
%%%
# portmaster -adf
...
gmake[2]: Leaving directory
'/usr/ports/work/usr/ports/graphics/svgalib/work/svgalib-1.4.3/doc'
Now run 'make demoprogs' to make the test and demo programs in demos/
and threedkit/.
gmake[1]: Leav
