hi
i see some mails in my inbox from pike-devel which are missing in the
online archive at
http://lists.lysator.liu.se/pipermail/pike-devel/2021-October/date.html
eg. the answers for "New Pike 8.0 release?" from william are missing
online.
yours
josef
hi
i'm currently building rpms of pike 8.0 for fedora35 and have troubles to
"install" the binaries.
my setup: mock (chroot environment for building rpms). inside of that
environment there are several steps, mainly extract source-files,
prepare, compile, install and collect the final
that did the trick
thanks
On Wed, 10 Nov 2021, Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum
wrote:
hi
Hi.
i'm currently building rpms of pike 8.0 for fedora35 and have troubles to
"install" the binaries.
my setup: mock (chroot environment for building rpms). inside of that
would be great
thanks for your work
On Tue, 26 Oct 2021, will...@welliver.org wrote:
It's been about a year since the last release, and I've found a number of
configure problems on "apple silicon". How about we start the process of a
new 8.0 release? Perhaps starting 2 weeks from today? If
> hi
Hi.
> i'm currently building rpms of pike 8.0 for fedora35 and have troubles to
> "install" the binaries.
>
> my setup: mock (chroot environment for building rpms). inside of that
> environment there are several steps, mainly extract source-files,
> prepare, compile, install and collect
The error code here (EPERM) is different from the one I was having
(ENOSYS), but hopefully the same fix should work here as well...
Actually, my vote is on removing this closefrom business completely.
If we can neither trust the function to succeed (as it is documented
to always do), nor reliably check whether or not it succeeded, then we
should not use it.
The assertion that a failed call will always succeed if you just try
