Hello Matthew, On Wed, Jun 16, 2021 at 12:58 AM Joel Sherrill <j...@rtems.org> wrote: > > @RTEMS_TOOLS_BIN@ should have been replaced with the real directory where > your RTEMS tools are located. Something like this:
Exactly. I was wondering the same when I saw his output of 'echo $PATH'. Matthew, the newlib and autoconf relationship is a bit messy. But you can simplify it if you use $PATH carefully. Have a look at this https://medium.com/my-gsoc-2019-journey/how-to-handle-two-versions-of-autoconf-b1e28de8617b, the path should expand and should point to the correct binaries. The blog should give you an idea of how the $PATH works and how it should be modified. -- Vaibhav Gupta > > $ export PATH=${HOME}/rtems-work/tools/6/bin:$PATH > > And to check you have the PATH right, do something like this: > > $ type sparc-rtems6-gcc > sparc-rtems6-gcc is /home/joel/rtems-work/tools/6/bin/sparc-rtems6-gcc > > On Tue, Jun 15, 2021 at 1:23 PM Eshan Dhawan <eshandhawa...@gmail.com> wrote: >> >> Hi matt >> It would work if run inside newlib instead of newlib-cygwin >> run command inside of ../newlib-cygwin/newlib >> instead of ../newlib-cygwin >> >> >> On Tue, Jun 15, 2021 at 10:59 PM Matthew Joyce <mfjoyce2...@gmail.com> wrote: >>> >>> Ah, ok will do! Thank you for the tip. >>> >>> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom <ged...@rtems.org> wrote: >>> > >>> > Just a note, it's more efficient to capture your terminal dump into a >>> > text file and attach that, rather than put a screenshot up. >>> > >>> > On Tue, Jun 15, 2021 at 11:14 AM Matthew Joyce <mfjoyce2...@gmail.com> >>> > wrote: >>> > > >>> > > Hi Gentlemen, >>> > > >>> > > Thanks very much for your quick replies! >>> > > >>> > > I just tried both, but perhaps I'm misinterpreting your suggestions. >>> > > (Could you please see the attached commands / errors!) >>> > > >>> > > Eshan, >>> > > >>> > > I did see that link, but it wasn't clear to me what the solution >>> > > was...Sorry! >>> > > >>> > > Sincerely, >>> > > >>> > > Matt >>> > > >>> > > On Tue, Jun 15, 2021 at 6:52 PM Eshan Dhawan <eshandhawa...@gmail.com> >>> > > wrote: >>> > > > >>> > > > Hi Matt, >>> > > > Try running the command with autoconf version 2.69 that's shipped >>> > > > with RTEMS in the rtems bin >>> > > > That works as well. >>> > > > >>> > > > Also From a quick google search this is what I found : >>> > > > https://superuser.com/questions/617872/cant-locate-autom4te-channeldefs-pm-in-inc-when-it-definitely-is-there >>> > > > >>> > > > On Tue, Jun 15, 2021 at 9:12 PM Matthew Joyce <mfjoyce2...@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? >>> > > >> >>> > > >> 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 >>> > > _______________________________________________ >>> > > devel mailing list >>> > > devel@rtems.org >>> > > http://lists.rtems.org/mailman/listinfo/devel >> >> _______________________________________________ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel