From: Chris Johns
- These additions let the net services repo build with the legacy
stack
---
include/machine/rtems-bsd-thread.h| 34 +
libc/gai_strerror.c | 125 +
libc/getaddrinfo.c| 3086 +
libc/nsswitch.h
From: Chris Johns
---
netlegacy.py | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/netlegacy.py b/netlegacy.py
index 9f27ffc..3ce54c6 100644
--- a/netlegacy.py
+++ b/netlegacy.py
@@ -104,6 +104,10 @@ def options(opt):
default='-O2',
From: Chris Johns
---
netlegacy.py | 2 ++
wscript | 1 -
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/netlegacy.py b/netlegacy.py
index 3ce54c6..c21e26c 100644
--- a/netlegacy.py
+++ b/netlegacy.py
@@ -165,6 +165,8 @@ def build(bld):
version_header(bld)
Hi,
The move of the networking header files to the system headers means
the functionality exposed is all that can be provided. This breaks the
backward compatibility of the legacy stack. The solution is to add
what is needed when needed to the legacy stack.
This patch adds getaddrinfo,
On 19/4/2023 11:26 pm, Frank Kühndel wrote:
> Hello Chris,
>
> thanks for the introduction to package build. On AlmaLinux the file
> rtems-source-builder/rtems/build/mipstx39-rtems6-gdb-13.1-x86_64-linux-gnu-1/build/gdb/config.log
> (attached) contains this error:
>
>
> configure:21340:
On 20/4/2023 12:57 am, Alex White wrote:
> This removes the ability to statically configure a second GPIO device.
> Instead, any number of GPIO devices can be configured using the device
> tree. If a device tree is not used, a single GPIO device can still be
> configured statically.
> ---
>
On 20/4/2023 7:42 am, Gedare Bloom wrote:
> On Mon, Apr 17, 2023 at 9:55 PM Chris Johns wrote:
>>
>> On 18/4/2023 1:48 pm, Gedare Bloom wrote:
>>> On Sun, Apr 16, 2023 at 6:48 PM Aaron Nyholm
>>> wrote:
As for the RTEMS_FLASHDEV_MAX_REGIONS being set at 32 I chose the value as
it
On Mon, Apr 17, 2023 at 9:55 PM Chris Johns wrote:
>
> On 18/4/2023 1:48 pm, Gedare Bloom wrote:
> > On Sun, Apr 16, 2023 at 6:48 PM Aaron Nyholm
> > wrote:
> >> As for the RTEMS_FLASHDEV_MAX_REGIONS being set at 32 I chose the value as
> >> it seamed a good balance between memory usage and
---
user/bsps/bsps-microblaze.rst | 19 +++
1 file changed, 19 insertions(+)
diff --git a/user/bsps/bsps-microblaze.rst b/user/bsps/bsps-microblaze.rst
index 3ad8179..0f28491 100644
--- a/user/bsps/bsps-microblaze.rst
+++ b/user/bsps/bsps-microblaze.rst
@@ -80,6 +80,15 @@ from
This removes the ability to statically configure a second GPIO device.
Instead, any number of GPIO devices can be configured using the device
tree. If a device tree is not used, a single GPIO device can still be
configured statically.
---
.../microblaze_fpga/gpio/microblaze-gpio.c| 188
Hello Chris,
thanks for the introduction to package build. On AlmaLinux the file
rtems-source-builder/rtems/build/mipstx39-rtems6-gdb-13.1-x86_64-linux-gnu-1/build/gdb/config.log
(attached) contains this error:
configure:21340: gcc -O2 -g -pipe
11 matches
Mail list logo