On 4/10/2018 8:54 PM, James Almer wrote:
> On 4/9/2018 11:35 AM, Derek Buitenhuis wrote:
>> On 4/9/2018 3:32 PM, James Almer wrote:
>>> Maybe they already know and it was fixed at some point, seeing the
>>> OpenBSD fate client we have has software from 2007 (gcc 4.2, and safe to
>>> assume equally
On 4/9/2018 11:35 AM, Derek Buitenhuis wrote:
> On 4/9/2018 3:32 PM, James Almer wrote:
>> Maybe they already know and it was fixed at some point, seeing the
>> OpenBSD fate client we have has software from 2007 (gcc 4.2, and safe to
>> assume equally outdated binutils).
>
> OpenBSD doesn't update
On 4/9/2018 3:32 PM, James Almer wrote:
> Maybe they already know and it was fixed at some point, seeing the
> OpenBSD fate client we have has software from 2007 (gcc 4.2, and safe to
> assume equally outdated binutils).
OpenBSD doesn't update their toolchain AFAIK, but maintains their own forks,
On 4/9/2018 11:15 AM, Derek Buitenhuis wrote:
> On 4/7/2018 10:58 PM, James Almer wrote:
>> It appears strip -o creates new files without preserving permissions
>> from the source binary, resulting in non executable files.
>
> This sounds like something the OpenBSD people should be informed of, no
On 4/7/2018 10:58 PM, James Almer wrote:
> It appears strip -o creates new files without preserving permissions
> from the source binary, resulting in non executable files.
This sounds like something the OpenBSD people should be informed of, no?
- Derek
___
It appears strip -o creates new files without preserving permissions
from the source binary, resulting in non executable files.
Signed-off-by: James Almer
---
Untested. This is purely based on what i see in http://fate.ffmpeg.org/
Alternatively, although probably much harder to do, would be to m
