Synchronize all file descriptors and not just the ones associated with a FILE
object.
Close #4656.
---
cpukit/libcsupport/src/sync.c | 84 +--
1 file changed, 12 insertions(+), 72 deletions(-)
diff --git a/cpukit/libcsupport/src/sync.c b/cpukit/libcsupport/src/syn
Sponsored-By: Precidata
---
rtems/config/tools/rtems-gcc-12-newlib-head.cfg | 7 +++
rtems/patches/fix-mac-arm64-isl-config.patch| 12
rtems/patches/fix-mac-arm64-mpc-config.patch| 13 +
rtems/patches/fix-mac-arm64-mpfr-config.patch | 12
4 fi
We do not put patches in RTEMS repos. File an rtems ticket, attach them,
and reference them from there.
If they are needed upstream, please submit them to the appropriate projects.
Otherwise, I can't test this so don't have much to say. Looks necessary
based on email discussions.
--joel
On Fri,
Joel,
I agree that having support upstreamed would be the best option. Due to
upstream lag behind apple hardware development I'm afraid we would miss
RTEMS 6 release if we would wait on upstream here, hence apple M1 users
would not be able to use RTEMS 6.
Hence offered short cut solution, j
On Fri, May 13, 2022, 9:08 AM Karel Gardas wrote:
>
> Joel,
>
> I agree that having support upstreamed would be the best option. Due to
> upstream lag behind apple hardware development I'm afraid we would miss
> RTEMS 6 release if we would wait on upstream here, hence apple M1 users
> would not b
On 13.05.22 16:25, Joel Sherrill wrote:
On Fri, May 13, 2022, 9:08 AM Karel Gardas wrote:
Joel,
I agree that having support upstreamed would be the best option. Due to
upstream lag behind apple hardware development I'm afraid we would miss
RTEMS 6 release if we would wait on upstream here, he
On Fri, May 13, 2022, 9:39 AM Cedric Berger wrote:
> On 13.05.22 16:25, Joel Sherrill wrote:
> > On Fri, May 13, 2022, 9:08 AM Karel Gardas
> wrote:
> >
> >> Joel,
> >>
> >> I agree that having support upstreamed would be the best option. Due to
> >> upstream lag behind apple hardware developmen
On 13.05.22 17:25, Joel Sherrill wrote:
I think you are missing my point. I'm not opposed to the patches and
understand the need.
The RTEMS Project tried putting patches in our git repos when the RSB
was new. It did not improve our diligence in getting them upstream or
removing them from our
On Fri, May 13, 2022 at 10:42 AM Cedric Berger wrote:
> On 13.05.22 17:25, Joel Sherrill wrote:
> > I think you are missing my point. I'm not opposed to the patches and
> > understand the need.
> >
> > The RTEMS Project tried putting patches in our git repos when the RSB
> > was new. It did not
On 13.05.22 17:55, Joel Sherrill wrote:
On Fri, May 13, 2022 at 10:42 AM Cedric Berger
wrote:
On 13.05.22 17:25, Joel Sherrill wrote:
> I think you are missing my point. I'm not opposed to the patches
and
> understand the need.
>
> The RTEMS Project tried putting patche
On 13/05/2022 18:06, Cedric Berger wrote:
No probem, I understand and it makes sense to put upstream, but again,
in that particular case, the real problem (autoconf) is already fixed
upstream.
The release managers of ISL, MPC, and MPFR need to know that they have
to make the next release with
I just discovered this when trying to update my CI that was running
Python 2.7. I have since bumped that to Python 3 to avoid the issue, but
the following patch resolves it.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/
It's possible for an environment to have unicode characters in its
paths. This was recently exposed by the latest newlib update and RSB
fails under Python 2.7 in this situation. This resolves the issue by
ensuring that the paths are encoded and decoded as necessary.
Related issue that caused the c
Hi
github has disabled the git protocol and wants people to use the https or
ssh protocol. There are a handful of github git:// URLs in the RSB master
and possibly more in the 5 branch. I have no idea right now what the rule
is to convert the URLs from git to https ones.
This is a warning to the
14 matches
Mail list logo
