GSOC POSIX Compliance: Stuck trying to build Newlib

[Joel Sherrill]

On Tue, Jun 15, 2021 at 10:42 AM Matthew Joyce <mfjoyce2004 at gmail.com>
wrote:

> Hello Dr. Joel and Eshan,
>
> I have a patch ready to send to Newlib for the sig function prototypes
> and STR2SIG_MAX.
>
> But to do that, I think I need to have Newlib built, which I must
> still be doing wrong. The error that I am getting is attached below.
>
> I’ve been trying to follow the steps here:
>
> https://medium.com/my-gsoc-2019-journey/apply-newlib-patch-to-rtems-source-builder-6873b0fb31b8
> and
> https://medium.com/my-gsoc-2019-journey/build-newlib-for-sparc-and-arm-architecture-6b3287d4c6f2
>
> I even had rebuilt everything from scratch to see if that would help,
> but I still get the same error. Maybe I cloned the newlib source into
> the wrong directory?
>

No. I suspect your PATH should have the autoconf version you want to
use at the head of your PATH. I tried this with the RTEMS autoconf at
the front of my PATH and it worked.

export PATH=@RTEMS_TOOLS_BIN@:${PATH}

It was changing way too many files. I would toss any changes that are
outside the directory you are working on.

If you are not adding or deleting a file, you don't have to do this. This
is only needed when the set of files and/or directories changes.


>
> I was hoping to get the patch off to Newlib for review as a first step
> while I work on writing the actual methods. When you get a moment,
> could you please advise? Thank you very much!
>
> Sincerely,
>
> Matt
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20210615/223c1a6b/attachment.html>