On 11.09.20 18:32, Philippe Gerum wrote:
>
> Jan Kiszka via Xenomai writes:
>
>> Hi all,
>>
>> to permit sharing the work of porting Xenomai over dovetail, I finally
>> pushed my baseline hacks to [1]. You can "use" that on [2] (use
>> fa1e9ba5e822, 0d68e5607286 leaks evl bits and is broken)
>
Jan Kiszka via Xenomai writes:
> Hi all,
>
> to permit sharing the work of porting Xenomai over dovetail, I finally
> pushed my baseline hacks to [1]. You can "use" that on [2] (use
> fa1e9ba5e822, 0d68e5607286 leaks evl bits and is broken)
Fixed on top of [2] now, thanks.
> just like you
>
On 11.09.20 11:43, Jan Leupold via Xenomai wrote:
> __open_2() and __open64_2() from glibc add runtime precondition tests for the
> 'oflag' parameter to the functionality of open()/open64(). They may be used
> when
> the macro _FORTIFY_SOURCE is defined when compiling the application code.
>
__open_2() and __open64_2() from glibc add runtime precondition tests for the
'oflag' parameter to the functionality of open()/open64(). They may be used when
the macro _FORTIFY_SOURCE is defined when compiling the application code. Added
these wrappers to cover those cases.
If Xenomai itself is
__open_2() and __open64_2() from glibc add runtime precondition tests for the
'oflag' parameter to the functionality of open()/open64(). They may be used when
the macro _FORTIFY_SOURCE is defined when compiling the application code. Added
these wrappers to cover those cases.
If Xenomai itself is
__open_2() and __open64_2() from glibc add runtime precondition tests for the
'oflag' parameter to the functionality of open()/open64(). They may be used when
the macro _FORTIFY_SOURCE is defined when compiling the application code. Added
these wrappers to cover those cases.
If Xenomai itself is
On 07.09.20 17:18, Philippe Gerum wrote:
>
> Philippe Gerum writes:
>
>> Jan Kiszka writes:
>>
>>> On 07.09.20 15:09, Philippe Gerum wrote:
From: Philippe Gerum
Signed-off-by: Philippe Gerum
---
arch/x86/kernel/ipipe.c | 1 +
1 file changed, 1 insertion(+)
Please consider for v3:
On 10.09.20 16:46, Jan Leupold via Xenomai wrote:
> __open_2() and __open64_2() from glibc add runtime precondition tests for the
> 'oflag' parameter to the functionality of open()/open64(). They may be used
> when
> the macro _FORTIFY_SOURCE is defined when compiling the
On 11.09.20 10:32, Jan Leupold via Xenomai wrote:
> If Xenomai itself is not compiled with FORTIFY_SOURCE then the function
> declarations for __open_2() and __open64_2() are not available.
> __STD(__open_2(...)) will not link in this case (would be a very special
> use case anyway?).
>
That
If Xenomai itself is not compiled with FORTIFY_SOURCE then the function
declarations for __open_2() and __open64_2() are not available.
__STD(__open_2(...)) will not link in this case (would be a very special
use case anyway?).
Signed-off-by: Jan Leupold
---
lib/cobalt/wrappers.c | 2 ++
1 file
Am 11.09.20 um 09:55 schrieb Jan Kiszka:
> On 11.09.20 08:22, Jan Leupold via Xenomai wrote:
>> Am 10.09.20 um 18:27 schrieb Jan Kiszka:
>>> On 10.09.20 18:14, Jan Kiszka via Xenomai wrote:
On 10.09.20 16:46, Jan Leupold via Xenomai wrote:
> __open_2() and __open64_2() from glibc add
On 11.09.20 08:22, Jan Leupold via Xenomai wrote:
> Am 10.09.20 um 18:27 schrieb Jan Kiszka:
>> On 10.09.20 18:14, Jan Kiszka via Xenomai wrote:
>>> On 10.09.20 16:46, Jan Leupold via Xenomai wrote:
__open_2() and __open64_2() from glibc add runtime precondition tests for
the
Am 10.09.20 um 18:27 schrieb Jan Kiszka:
> On 10.09.20 18:14, Jan Kiszka via Xenomai wrote:
>> On 10.09.20 16:46, Jan Leupold via Xenomai wrote:
>>> __open_2() and __open64_2() from glibc add runtime precondition tests for
>>> the
>>> 'oflag' parameter to the functionality of open()/open64().
Download URL:
https://xenomai.org/downloads/ipipe/v4.x/x86/ipipe-core-4.19.140-cip33-x86-14.patch
Repository: https://git.xenomai.org/ipipe-x86
Release tag: ipipe-core-4.19.140-cip33-x86-14
14 matches
Mail list logo
