Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Matthew Joyce
Ok, thanks!

I'm about to sign off for dinner,  but I'll send the patch (with
disclaimer) tonight.  So since the code fails to compile, I need to
start making some changes. Do I need to rebuild the rtems tool chain
each time? I'm averaging about 1.33 hours on that :-( . Is that where
some of the scripts you sent help out?

Sorry we didn't connect tonight, but please let me know if there's
another day this week you could chat!

Thanks so much for everybody's patience and support!

Sincerely,

Matt

On Wed, Jun 16, 2021 at 6:43 PM Joel Sherrill  wrote:
>
>
>
> On Wed, Jun 16, 2021 at 11:37 AM Matthew Joyce  wrote:
>>
>> I hate to ask, but where should the build binaries be if "make all"
>> was actually successful?
>
>
> For newlib, there should be various libc.a and libm.a files in the build 
> directory.
>
> Use find to locate them: find . -name libc.a
>
> And use "nm" to find out if the symbol is there.
>
> sparc-rtems6-nm .../libc.a
>
> You can save that output or pipe it to less.
>
> Note: paths need to be adjusted to the files.
>
> --joel
>>
>>
>> Thanks!
>>
>> Matt
>>
>> On Wed, Jun 16, 2021 at 6:16 PM Eshan Dhawan  wrote:
>> >
>> > Hi Matt,
>> > > On 16-Jun-2021, at 9:27 PM, Matthew Joyce  wrote:
>> > >
>> > > Hi Dr. Joel,
>> > >
>> > > I tried that in newlib/libc and there were at least no errors.
>> > > (Nothing leading me to believe it was successful either!)
>> > >
>> > > However I still got the same error when I sudo make install.
>> > > (sparc-rtems-ranlib: command not found) (among others!)
>> > >
>> > I make works then there is no need to run make install it just copies the 
>> > build binaries to the root folders.
>> >
>> > If make is build with the changes u made and the symbols that you added 
>> > appear in the binaries you generated.
>> > Then congratulations :)
>> > Now you just need to test those changes in the RSB to test they don’t 
>> > break anything in the RTEMS ecosystem.
>> > > Thanks again!
>> > >
>> > > Sincerely,
>> > >
>> > > Matt
>> > >
>> > >
>> > >
>> > >> On Wed, Jun 16, 2021 at 3:06 PM Joel Sherrill  wrote:
>> > >>
>> > >> Does adding --no-recursive and running it only from the directory you 
>> > >> touched a build system file in help?
>> > >>
>> > >> It is regenerating a lot you don't want to touch anyway.
>> > >>
>> > >> --joel
>> > >>
>> > >>> On Wed, Jun 16, 2021, 5:32 AM Matthew Joyce  
>> > >>> wrote:
>> > >>>
>> > >>> Hi Eshan,
>> > >>>
>> > >>> Thanks very much for your follow up! Ok, I see now that if I go into
>> > >>> development/newlib/newlib-cygwin/newlib and run autoreconf -fvi with
>> > >>> the v2.69 using the PATH that Dr. Joel just showed, it starts to run.
>> > >>> It always eventually exits with an error though. (please see attached
>> > >>> .txt). I hope you can read that...I used the command "script" to
>> > >>> output everything to a text file.
>> > >>>
>> > >>> Do you have any idea where I might be going wrong?
>> > >>>
>> > >>> Thank you!
>> > >>>
>> > >>> Sincerely,
>> > >>>
>> > >>> Matt
>> > >>>
>> > >>> On Tue, Jun 15, 2021 at 8:23 PM Eshan Dhawan  
>> > >>> 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 
>> >   wrote:
>> > >
>> > > Ah, ok will do! Thank you for the tip.
>> > >
>> > > On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  
>> > > 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 
>> > >>  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 
>> > >>>  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 
>> >   wrote:
>> > >
>> > > Hello Dr. Joel and Eshan,
>> > >
>> > > I have a patch ready to 

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Joel Sherrill
On Wed, Jun 16, 2021 at 11:37 AM Matthew Joyce 
wrote:

> I hate to ask, but where should the build binaries be if "make all"
> was actually successful?
>

For newlib, there should be various libc.a and libm.a files in the build
directory.

Use find to locate them: find . -name libc.a

And use "nm" to find out if the symbol is there.

sparc-rtems6-nm .../libc.a

You can save that output or pipe it to less.

Note: paths need to be adjusted to the files.

--joel

>
> Thanks!
>
> Matt
>
> On Wed, Jun 16, 2021 at 6:16 PM Eshan Dhawan 
> wrote:
> >
> > Hi Matt,
> > > On 16-Jun-2021, at 9:27 PM, Matthew Joyce 
> wrote:
> > >
> > > Hi Dr. Joel,
> > >
> > > I tried that in newlib/libc and there were at least no errors.
> > > (Nothing leading me to believe it was successful either!)
> > >
> > > However I still got the same error when I sudo make install.
> > > (sparc-rtems-ranlib: command not found) (among others!)
> > >
> > I make works then there is no need to run make install it just copies
> the build binaries to the root folders.
> >
> > If make is build with the changes u made and the symbols that you added
> appear in the binaries you generated.
> > Then congratulations :)
> > Now you just need to test those changes in the RSB to test they don’t
> break anything in the RTEMS ecosystem.
> > > Thanks again!
> > >
> > > Sincerely,
> > >
> > > Matt
> > >
> > >
> > >
> > >> On Wed, Jun 16, 2021 at 3:06 PM Joel Sherrill  wrote:
> > >>
> > >> Does adding --no-recursive and running it only from the directory you
> touched a build system file in help?
> > >>
> > >> It is regenerating a lot you don't want to touch anyway.
> > >>
> > >> --joel
> > >>
> > >>> On Wed, Jun 16, 2021, 5:32 AM Matthew Joyce 
> wrote:
> > >>>
> > >>> Hi Eshan,
> > >>>
> > >>> Thanks very much for your follow up! Ok, I see now that if I go into
> > >>> development/newlib/newlib-cygwin/newlib and run autoreconf -fvi with
> > >>> the v2.69 using the PATH that Dr. Joel just showed, it starts to run.
> > >>> It always eventually exits with an error though. (please see attached
> > >>> .txt). I hope you can read that...I used the command "script" to
> > >>> output everything to a text file.
> > >>>
> > >>> Do you have any idea where I might be going wrong?
> > >>>
> > >>> Thank you!
> > >>>
> > >>> Sincerely,
> > >>>
> > >>> Matt
> > >>>
> > >>> On Tue, Jun 15, 2021 at 8: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 
> 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 

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Matthew Joyce
I hate to ask, but where should the build binaries be if "make all"
was actually successful?

Thanks!

Matt

On Wed, Jun 16, 2021 at 6:16 PM Eshan Dhawan  wrote:
>
> Hi Matt,
> > On 16-Jun-2021, at 9:27 PM, Matthew Joyce  wrote:
> >
> > Hi Dr. Joel,
> >
> > I tried that in newlib/libc and there were at least no errors.
> > (Nothing leading me to believe it was successful either!)
> >
> > However I still got the same error when I sudo make install.
> > (sparc-rtems-ranlib: command not found) (among others!)
> >
> I make works then there is no need to run make install it just copies the 
> build binaries to the root folders.
>
> If make is build with the changes u made and the symbols that you added 
> appear in the binaries you generated.
> Then congratulations :)
> Now you just need to test those changes in the RSB to test they don’t break 
> anything in the RTEMS ecosystem.
> > Thanks again!
> >
> > Sincerely,
> >
> > Matt
> >
> >
> >
> >> On Wed, Jun 16, 2021 at 3:06 PM Joel Sherrill  wrote:
> >>
> >> Does adding --no-recursive and running it only from the directory you 
> >> touched a build system file in help?
> >>
> >> It is regenerating a lot you don't want to touch anyway.
> >>
> >> --joel
> >>
> >>> On Wed, Jun 16, 2021, 5:32 AM Matthew Joyce  wrote:
> >>>
> >>> Hi Eshan,
> >>>
> >>> Thanks very much for your follow up! Ok, I see now that if I go into
> >>> development/newlib/newlib-cygwin/newlib and run autoreconf -fvi with
> >>> the v2.69 using the PATH that Dr. Joel just showed, it starts to run.
> >>> It always eventually exits with an error though. (please see attached
> >>> .txt). I hope you can read that...I used the command "script" to
> >>> output everything to a text file.
> >>>
> >>> Do you have any idea where I might be going wrong?
> >>>
> >>> Thank you!
> >>>
> >>> Sincerely,
> >>>
> >>> Matt
> >>>
> >>> On Tue, Jun 15, 2021 at 8:23 PM Eshan Dhawan  
> >>> 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  
>  wrote:
> >
> > Ah, ok will do! Thank you for the tip.
> >
> > On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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  
> >> 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 
> >>>  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 
>   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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Joel Sherrill
On Wed, Jun 16, 2021 at 11:16 AM Eshan Dhawan 
wrote:

> Hi Matt,
> > On 16-Jun-2021, at 9:27 PM, Matthew Joyce  wrote:
> >
> > Hi Dr. Joel,
> >
> > I tried that in newlib/libc and there were at least no errors.
> > (Nothing leading me to believe it was successful either!)
> >
> > However I still got the same error when I sudo make install.
> > (sparc-rtems-ranlib: command not found) (among others!)
> >
> I make works then there is no need to run make install it just copies the
> build binaries to the root folders.
>
> If make is build with the changes u made and the symbols that you added
> appear in the binaries you generated.
> Then congratulations :)
> Now you just need to test those changes in the RSB to test they don’t
> break anything in the RTEMS ecosystem.


Or use the same prefix as you did with the RSB installed tools and begin to
add a test to RTEMS for the method.

When you add to newlib and need a test in RTEMS for that functionality, you
end up with a pair of patches. First the newlib one has to be merged, then
your test can be added to RTEMS.

--joel


>
> > Thanks again!
> >
> > Sincerely,
> >
> > Matt
> >
> >
> >
> >> On Wed, Jun 16, 2021 at 3:06 PM Joel Sherrill  wrote:
> >>
> >> Does adding --no-recursive and running it only from the directory you
> touched a build system file in help?
> >>
> >> It is regenerating a lot you don't want to touch anyway.
> >>
> >> --joel
> >>
> >>> On Wed, Jun 16, 2021, 5:32 AM Matthew Joyce 
> wrote:
> >>>
> >>> Hi Eshan,
> >>>
> >>> Thanks very much for your follow up! Ok, I see now that if I go into
> >>> development/newlib/newlib-cygwin/newlib and run autoreconf -fvi with
> >>> the v2.69 using the PATH that Dr. Joel just showed, it starts to run.
> >>> It always eventually exits with an error though. (please see attached
> >>> .txt). I hope you can read that...I used the command "script" to
> >>> output everything to a text file.
> >>>
> >>> Do you have any idea where I might be going wrong?
> >>>
> >>> Thank you!
> >>>
> >>> Sincerely,
> >>>
> >>> Matt
> >>>
> >>> On Tue, Jun 15, 2021 at 8:23 PM Eshan Dhawan 
> 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 
> wrote:
> >
> > Ah, ok will do! Thank you for the tip.
> >
> > On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom 
> 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
> >>> 

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Eshan Dhawan
Hi Matt,
> On 16-Jun-2021, at 9:27 PM, Matthew Joyce  wrote:
> 
> Hi Dr. Joel,
> 
> I tried that in newlib/libc and there were at least no errors.
> (Nothing leading me to believe it was successful either!)
> 
> However I still got the same error when I sudo make install.
> (sparc-rtems-ranlib: command not found) (among others!)
> 
I make works then there is no need to run make install it just copies the build 
binaries to the root folders.

If make is build with the changes u made and the symbols that you added appear 
in the binaries you generated.
Then congratulations :) 
Now you just need to test those changes in the RSB to test they don’t break 
anything in the RTEMS ecosystem. 
> Thanks again!
> 
> Sincerely,
> 
> Matt
> 
> 
> 
>> On Wed, Jun 16, 2021 at 3:06 PM Joel Sherrill  wrote:
>> 
>> Does adding --no-recursive and running it only from the directory you 
>> touched a build system file in help?
>> 
>> It is regenerating a lot you don't want to touch anyway.
>> 
>> --joel
>> 
>>> On Wed, Jun 16, 2021, 5:32 AM Matthew Joyce  wrote:
>>> 
>>> Hi Eshan,
>>> 
>>> Thanks very much for your follow up! Ok, I see now that if I go into
>>> development/newlib/newlib-cygwin/newlib and run autoreconf -fvi with
>>> the v2.69 using the PATH that Dr. Joel just showed, it starts to run.
>>> It always eventually exits with an error though. (please see attached
>>> .txt). I hope you can read that...I used the command "script" to
>>> output everything to a text file.
>>> 
>>> Do you have any idea where I might be going wrong?
>>> 
>>> Thank you!
>>> 
>>> Sincerely,
>>> 
>>> Matt
>>> 
>>> On Tue, Jun 15, 2021 at 8:23 PM Eshan Dhawan  
>>> 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  
 wrote:
> 
> Ah, ok will do! Thank you for the tip.
> 
> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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  
>> 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  
>>> 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  
 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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Matthew Joyce
Hi Dr. Joel,

I used the following, based on Vaibhav's blog:

$ export PATH=$HOME/development/rtems/6/bin:$PATH

$ ../newlib-cygwin/configure --target=sparc-rtems6 --disable-shared
--disable-nls --enable-werror --enable-newlib-supplied-syscalls
--enable-interwork --enable-multilib --with-gnu-as --with-gnu-ld

When I enter "type sparc-rtems6-gcc" (I hope I'm understanding that
correctly!), I get sparc-rtems6-gcc is hashed...and then my PATH.

Thanks again!

V/r,

Matt

On Wed, Jun 16, 2021 at 6:06 PM Joel Sherrill  wrote:
>
>
>
> On Wed, Jun 16, 2021 at 10:57 AM Matthew Joyce  wrote:
>>
>> Hi Dr. Joel,
>>
>> I tried that in newlib/libc and there were at least no errors.
>> (Nothing leading me to believe it was successful either!)
>>
>> However I still got the same error when I sudo make install.
>> (sparc-rtems-ranlib: command not found) (among others!)
>
>
> The target should be sparc-rtems6 when you configure newlib.
> This should mean invoking the script like "./j-newlib sparc-rtems6"
>
>
> And the RTEMS tools should be in your PATH.
>
> type sparc-rtems6-gcc
>
> To be sure.
>
> --joel
>>
>>
>> Thanks again!
>>
>> Sincerely,
>>
>> Matt
>>
>>
>>
>> On Wed, Jun 16, 2021 at 3:06 PM Joel Sherrill  wrote:
>> >
>> > Does adding --no-recursive and running it only from the directory you 
>> > touched a build system file in help?
>> >
>> > It is regenerating a lot you don't want to touch anyway.
>> >
>> > --joel
>> >
>> > On Wed, Jun 16, 2021, 5:32 AM Matthew Joyce  wrote:
>> >>
>> >> Hi Eshan,
>> >>
>> >> Thanks very much for your follow up! Ok, I see now that if I go into
>> >> development/newlib/newlib-cygwin/newlib and run autoreconf -fvi with
>> >> the v2.69 using the PATH that Dr. Joel just showed, it starts to run.
>> >> It always eventually exits with an error though. (please see attached
>> >> .txt). I hope you can read that...I used the command "script" to
>> >> output everything to a text file.
>> >>
>> >> Do you have any idea where I might be going wrong?
>> >>
>> >> Thank you!
>> >>
>> >> Sincerely,
>> >>
>> >> Matt
>> >>
>> >> On Tue, Jun 15, 2021 at 8:23 PM Eshan Dhawan  
>> >> 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  
>> >> > wrote:
>> >> >>
>> >> >> Ah, ok will do! Thank you for the tip.
>> >> >>
>> >> >> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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 
>> >> >> >  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 
>> >> >> > >  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 
>> >> >> > > >  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 
>> >> >> > 

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Joel Sherrill
On Wed, Jun 16, 2021 at 10:57 AM Matthew Joyce 
wrote:

> Hi Dr. Joel,
>
> I tried that in newlib/libc and there were at least no errors.
> (Nothing leading me to believe it was successful either!)
>
> However I still got the same error when I sudo make install.
> (sparc-rtems-ranlib: command not found) (among others!)
>

The target should be sparc-rtems6 when you configure newlib.
This should mean invoking the script like "./j-newlib sparc-rtems6"


And the RTEMS tools should be in your PATH.

type sparc-rtems6-gcc

To be sure.

--joel

>
> Thanks again!
>
> Sincerely,
>
> Matt
>
>
>
> On Wed, Jun 16, 2021 at 3:06 PM Joel Sherrill  wrote:
> >
> > Does adding --no-recursive and running it only from the directory you
> touched a build system file in help?
> >
> > It is regenerating a lot you don't want to touch anyway.
> >
> > --joel
> >
> > On Wed, Jun 16, 2021, 5:32 AM Matthew Joyce 
> wrote:
> >>
> >> Hi Eshan,
> >>
> >> Thanks very much for your follow up! Ok, I see now that if I go into
> >> development/newlib/newlib-cygwin/newlib and run autoreconf -fvi with
> >> the v2.69 using the PATH that Dr. Joel just showed, it starts to run.
> >> It always eventually exits with an error though. (please see attached
> >> .txt). I hope you can read that...I used the command "script" to
> >> output everything to a text file.
> >>
> >> Do you have any idea where I might be going wrong?
> >>
> >> Thank you!
> >>
> >> Sincerely,
> >>
> >> Matt
> >>
> >> On Tue, Jun 15, 2021 at 8:23 PM Eshan Dhawan 
> 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 
> wrote:
> >> >>
> >> >> Ah, ok will do! Thank you for the tip.
> >> >>
> >> >> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom 
> 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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Matthew Joyce
Hi Dr. Joel,

I tried that in newlib/libc and there were at least no errors.
(Nothing leading me to believe it was successful either!)

However I still got the same error when I sudo make install.
(sparc-rtems-ranlib: command not found) (among others!)

Thanks again!

Sincerely,

Matt



On Wed, Jun 16, 2021 at 3:06 PM Joel Sherrill  wrote:
>
> Does adding --no-recursive and running it only from the directory you touched 
> a build system file in help?
>
> It is regenerating a lot you don't want to touch anyway.
>
> --joel
>
> On Wed, Jun 16, 2021, 5:32 AM Matthew Joyce  wrote:
>>
>> Hi Eshan,
>>
>> Thanks very much for your follow up! Ok, I see now that if I go into
>> development/newlib/newlib-cygwin/newlib and run autoreconf -fvi with
>> the v2.69 using the PATH that Dr. Joel just showed, it starts to run.
>> It always eventually exits with an error though. (please see attached
>> .txt). I hope you can read that...I used the command "script" to
>> output everything to a text file.
>>
>> Do you have any idea where I might be going wrong?
>>
>> Thank you!
>>
>> Sincerely,
>>
>> Matt
>>
>> On Tue, Jun 15, 2021 at 8:23 PM Eshan Dhawan  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  
>> > wrote:
>> >>
>> >> Ah, ok will do! Thank you for the tip.
>> >>
>> >> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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  
>> >> > 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 
>> >> > >  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 
>> >> > > >  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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Joel Sherrill
Does adding --no-recursive and running it only from the directory you
touched a build system file in help?

It is regenerating a lot you don't want to touch anyway.

--joel

On Wed, Jun 16, 2021, 5:32 AM Matthew Joyce  wrote:

> Hi Eshan,
>
> Thanks very much for your follow up! Ok, I see now that if I go into
> development/newlib/newlib-cygwin/newlib and run autoreconf -fvi with
> the v2.69 using the PATH that Dr. Joel just showed, it starts to run.
> It always eventually exits with an error though. (please see attached
> .txt). I hope you can read that...I used the command "script" to
> output everything to a text file.
>
> Do you have any idea where I might be going wrong?
>
> Thank you!
>
> Sincerely,
>
> Matt
>
> On Tue, Jun 15, 2021 at 8:23 PM Eshan Dhawan 
> 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 
> wrote:
> >>
> >> Ah, ok will do! Thank you for the tip.
> >>
> >> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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 
> 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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Matthew Joyce
Hi Eshan,

Thanks very much for your follow up! Ok, I see now that if I go into
development/newlib/newlib-cygwin/newlib and run autoreconf -fvi with
the v2.69 using the PATH that Dr. Joel just showed, it starts to run.
It always eventually exits with an error though. (please see attached
.txt). I hope you can read that...I used the command "script" to
output everything to a text file.

Do you have any idea where I might be going wrong?

Thank you!

Sincerely,

Matt

On Tue, Jun 15, 2021 at 8:23 PM Eshan Dhawan  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  wrote:
>>
>> Ah, ok will do! Thank you for the tip.
>>
>> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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  
>> > 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  
>> > > 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  
>> > > > 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
Script started on 2021-06-16 11:49:24+02:00 [TERM="xterm-256color" 
TTY="/dev/pts/0" COLUMNS="129" LINES="33"]
]777;notify;Command 
completed;exit\]777;precmd\]0;mj@fedora:~/development/newlib/newlib-cygwin/newlib\]7;file://fedora/home/mj/development/newlib/newlib-cygwin/newlib\[mj@localhost
 newlib]$ cd ~/development/newlib/newlib-cygwin/newlib/
]777;preexec\]777;notify;Command completed;cd 
~/development/newlib/newlib-cygwin/newlib/\]777;precmd\]0;mj@fedora:~/development/newlib/newlib-cygwin/newlib\]7;file://fedora/home/mj/development/newlib/newlib-cygwin/newlib\[mj@localhost
 newlib]$ autoconf -V
]777;preexec\autoconf (GNU Autoconf) 2.64
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.
]777;notify;Command completed;autoconf 
-V\]777;precmd\]0;mj@fedora:~/development/newlib/newlib-cygwin/newlib\]7;file://fedora/home/mj/development/newlib/newlib-cygwin/newlib\[mj@localhost
 newlib]$ echo $PATH
]777;preexec\/opt/autoconf-2.64/bin:/home/mj/.local/bin:/home/mj/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin
]777;notify;Command completed;echo 
$PATH\]777;precmd\]0;mj@fedora:~/development/newlib/newlib-cygwin/newlib\]7;file://fedora/home/mj/development/newlib/newlib-cygwin/newlib\[mj@localhost
 newlib]$ autoreconf =-fvi
]777;preexec\Can't locate Autom4te/ChannelDefs.pm in @INC (you may need to 
install the Autom4te::ChannelDefs module) (@INC contains: 
/usr/local/share/autoconf /usr/local/lib64/perl5/5.32 
/usr/local/share/perl5/5.32 

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-16 Thread Matthew Joyce
Hi Vaibhav,

Thanks very much for your note!  Fantastic job on your blogs. I read
the entry on managing the two versions of autoconf and have been
trying to follow it carefully. Could you please see the attached txt
file?

I'm in development/newlib/newlib-cygwin. I get the error where it
tells me to use exactly autoconf 2.64 and not 2.69. I change the $PATH
to make sure it is checking the opt/autoconf-2.64/bin first.

I check the autoconf version and confirm that it is now using 2.64.
But then when I try to run autoreconf -fvi, I get the same error as I
had yesterday.

Do you have any ideas as to what I'm doing wrong?

Thanks again!

Sincerely,

Matt

On Wed, Jun 16, 2021 at 4:36 AM Vaibhav Gupta  wrote:
>
> Hello Matthew,
>
> On Wed, Jun 16, 2021 at 12:58 AM Joel Sherrill  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  
> > 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  
> >> wrote:
> >>>
> >>> Ah, ok will do! Thank you for the tip.
> >>>
> >>> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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  
> >>> > 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 
> >>> > >  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 
> >>> > > >  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
> > 

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-15 Thread Vaibhav Gupta
Hello Matthew,

On Wed, Jun 16, 2021 at 12:58 AM Joel Sherrill  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  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  wrote:
>>>
>>> Ah, ok will do! Thank you for the tip.
>>>
>>> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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  
>>> > 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  
>>> > > 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  
>>> > > > 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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-15 Thread Joel Sherrill
@RTEMS_TOOLS_BIN@ should have been replaced with the real directory where
your RTEMS tools are located. Something like this:

$ 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 
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 
> wrote:
>
>> Ah, ok will do! Thank you for the tip.
>>
>> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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 
>> 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 
>> 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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-15 Thread Eshan Dhawan
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 
wrote:

> Ah, ok will do! Thank you for the tip.
>
> On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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 
> 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 
> 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 
> 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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-15 Thread Matthew Joyce
Ah, ok will do! Thank you for the tip.

On Tue, Jun 15, 2021 at 7:17 PM Gedare Bloom  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  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  
> > 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  
> > > 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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-15 Thread Gedare Bloom
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  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  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  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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-15 Thread Matthew Joyce
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  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  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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-15 Thread Eshan Dhawan
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  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

Re: GSOC POSIX Compliance: Stuck trying to build Newlib

2021-06-15 Thread Joel Sherrill
On Tue, Jun 15, 2021 at 10:42 AM Matthew Joyce 
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
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel