<div dir="auto">Hi Vijay,<div dir="auto"><br></div><div dir="auto">Will send a v3 soon</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 20 Mar 2021, 7:07 am Gedare Bloom, <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Ida,<br>
<br>
On Wed, Mar 17, 2021 at 11:36 PM Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank" rel="noreferrer">gedare@rtems.org</a>> wrote:<br>
><br>
> On Wed, Mar 17, 2021 at 9:04 PM Vijay Kumar Banerjee <<a href="mailto:vijay@rtems.org" target="_blank" rel="noreferrer">vijay@rtems.org</a>> wrote:<br>
> ><br>
> > Hello Ida,<br>
> ><br>
> ><br>
> > On Wed, Mar 17, 2021 at 8:42 PM Ida Delphine <<a href="mailto:idadelm@gmail.com" target="_blank" rel="noreferrer">idadelm@gmail.com</a>> wrote:<br>
> > ><br>
> > > I just installed texlive and trying to do a top level build using ./waf configure. But looks like it doesn't work well...I get this error at the end:<br>
> > > Setting top to : /home/idadel/Desktop/gsoc/docs/rtems-docs<br>
> > > Setting out to : /home/idadel/Desktop/gsoc/docs/rtems-docs/build<br>
> > > Checking for program 'git' : /usr/bin/git<br>
> > > Checking for program 'sphinx-build' : /home/idadel/anaconda3/bin/sphinx-build<br>
> > > Checking for program 'aspell' : /usr/bin/aspell<br>
> > > Checking if Sphinx is at least 1.3 : yes (3.5)<br>
> > > Checking Sphinx Options : none<br>
> > > Checking Sphinx Nit-Pick mode : no<br>
> > > Checking for 'sphinx.ext.autodoc' : found<br>
> > > Checking for 'sphinx.ext.coverage' : found<br>
> > > Checking for 'sphinx.ext.doctest' : found<br>
> > > Checking for 'sphinx.ext.graphviz' : found<br>
> > > Checking for 'sphinx.ext.intersphinx' : found<br>
> > > Checking for 'sphinx.ext.mathjax' : found<br>
> > > Checking for 'sphinxcontrib.bibtex' : not found (see README.txt)<br>
> ><br>
<br>
Did you manage to get past this yet? After you confirm you can build<br>
and see the changes for your pending documentation (example output)<br>
patch series, if you're happy with the ones on the list just ping one<br>
of them, or if you want to resend another version then prepare it with<br>
the -v3 I guess it would be by now.<br>
<br>
> > This looks like a helpful error message ;)<br>
> > In the README.txt you'll find the "Host set up" section that has some instructions about the required packages: <a href="https://git.rtems.org/rtems-docs/tree/README.txt#n92" rel="noreferrer noreferrer" target="_blank">https://git.rtems.org/rtems-docs/tree/README.txt#n92</a><br>
> ><br>
> > The short answer to your question:<br>
> > pip install sphinx<br>
> > pip install sphinxcontrib-bibtex<br>
> ><br>
><br>
> I also strongly recommend following those README directions to do the<br>
> build within a virtualenv if you haven't been. This will help better<br>
> manage the python versions in use. (My host's native python<br>
> installation is broken quite badly, but virtualenv works well.)<br>
><br>
> ><br>
> > Best regards,<br>
> > Vijay<br>
> ><br>
> > > The configuration failed<br>
> > > (complete log in /home/idadel/Desktop/gsoc/docs/rtems-docs/build/config.log)<br>
> > ><br>
> > > On Wed, Mar 17, 2021 at 9:37 PM Ida Delphine <<a href="mailto:idadelm@gmail.com" target="_blank" rel="noreferrer">idadelm@gmail.com</a>> wrote:<br>
> > >><br>
> > >> Ok, I will do that.<br>
> > >><br>
> > >> On Tue, Mar 16, 2021 at 7:56 PM Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank" rel="noreferrer">gedare@rtems.org</a>> wrote:<br>
> > >>><br>
> > >>> On Tue, Mar 16, 2021 at 12:16 PM Ida Delphine <<a href="mailto:idadelm@gmail.com" target="_blank" rel="noreferrer">idadelm@gmail.com</a>> wrote:<br>
> > >>> ><br>
> > >>> > I ran the commands and copied and pasted wherever there were mismatches especially with respect to the version numbers.<br>
> > >>> ><br>
> > >>> OK, I noticed some inconsistencies and was wondering. It would be<br>
> > >>> better to provide the actual output for the entire snippets, see<br>
> > >>> further below what I noticed.<br>
> > >>><br>
> > >>> > Should I resend the patchset with a better commit message?<br>
> > >>> ><br>
> > >>> Yes. I think it would be better to also update the entire output<br>
> > >>> examples, and to separate them from the manual changes you make to the<br>
> > >>> version numbers. In other words, update the version numbers by hand<br>
> > >>> for some things, and update the console output examples separately.<br>
> > >>> You can put multiple changes together in one patch that are related,<br>
> > >>> for example you might just send one patch with all the console output<br>
> > >>> example updates.<br>
> > >>><br>
> > >>> > On Tue, 16 Mar 2021, 6:50 pm Gedare Bloom, <<a href="mailto:gedare@rtems.org" target="_blank" rel="noreferrer">gedare@rtems.org</a>> wrote:<br>
> > >>> >><br>
> > >>> >> Hi Ida,<br>
> > >>> >><br>
> > >>> >> Since the patches now indicate rtems-docs, you don't need to include<br>
> > >>> >> that in the commit message. Instead, it is recommended to put the<br>
> > >>> >> manual directory name that is modified as the first part of the<br>
> > >>> >> commit, e.g., "user: bump version 5 to 6 in start/tools.rst"<br>
> > >>> >><br>
> > >>> >> More below:<br>
> > >>> >><br>
> > >>> >> On Tue, Mar 16, 2021 at 2:16 AM Ida Delphine <<a href="mailto:idadelm@gmail.com" target="_blank" rel="noreferrer">idadelm@gmail.com</a>> wrote:<br>
> > >>> >> ><br>
> > >>> >> > Edit edit sample output of tool suite installation.<br>
> > >>> >> > Edit command to check if C cross compiler works and sample output of this command.<br>
> > >>> >> > ---<br>
> > >>> >> > user/start/tools.rst | 26 +++++++++++++-------------<br>
> > >>> >> > 1 file changed, 13 insertions(+), 13 deletions(-)<br>
> > >>> >> ><br>
> > >>> >> > diff --git a/user/start/tools.rst b/user/start/tools.rst<br>
> > >>> >> > index baa2387..9a915ab 100644<br>
> > >>> >> > --- a/user/start/tools.rst<br>
> > >>> >> > +++ b/user/start/tools.rst<br>
> > >>> >> > @@ -12,7 +12,7 @@ Install the Tool Suite<br>
> > >>> >> ><br>
> > >>> >> > You have chosen an installation prefix, the BSP to build, the tool's<br>
> > >>> >> > architecure and prepared the source for the RSB in the previous sections. We<br>
> > >>> unrelated, fix typo: architecture<br>
> > >>><br>
> > >>> >> > -have chosen :file:`$HOME/quick-start/rtems/5` as the installation prefix, the<br>
> > >>> >> > +have chosen :file:`$HOME/quick-start/rtems/6` as the installation prefix, the<br>
> > >>> >> > ``erc32`` BSP and the SPARC architecture name of ``sparc-rtems5``, and unpacked<br>
> > >>> >> > the RSB source in :file:`$HOME/quick-start/src`.<br>
> > >>> >> ><br>
> > >>> >> > @@ -25,7 +25,7 @@ Build and install the tool suite:<br>
> > >>> >> > .. code-block:: none<br>
> > >>> >> ><br>
> > >>> >> > cd $HOME/quick-start/src/rsb/rtems<br>
> > >>> >> > - ../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5 5/rtems-sparc<br>
> > >>> >> > + ../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6 6/rtems-sparc<br>
> > >>> >> ><br>
> > >>> >> > This command should output something like this (omitted lines are denoted by<br>
> > >>> >> > ...). The build host appears as part of the name of the package being<br>
> > >>> >> > @@ -33,19 +33,19 @@ built. The name you see may vary depending on the host you are using:<br>
> > >>> >> ><br>
> > >>> >> > .. code-block:: none<br>
> > >>> >> ><br>
> > >>> >> > - RTEMS Source Builder - Set Builder, 5.1.0<br>
> > >>> >> > - Build Set: 5/rtems-sparc<br>
> > >>> >> > + RTEMS Source Builder - Set Builder, 6<br>
> > >>> >> > + Build Set: 6/rtems-sparc<br>
> > >>> >> > ...<br>
> > >>> >> > config: tools/rtems-binutils-2.34.cfg<br>
> > >>> >> > - package: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1<br>
> > >>> >> > - building: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1<br>
> > >>> >> > - sizes: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1: 305.866MB (installed: 29.966MB)<br>
> > >>> >> > - cleaning: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1<br>
> > >>> >> > + package: sparc-rtems6=-binutils-2.34-x86_64-freebsd12.1-1<br>
> > >>><br>
> > >>> The = sign here is what got me thinking something odd is going on.<br>
> > >>> Please copy-paste the entire output/snippet you get, and update the<br>
> > >>> examples completely so that each snippet is self-consistent at least.<br>
> > >>><br>
> > >>> >> > + building: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1<br>
> > >>> >> > + sizes: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1: 305.866MB (installed: 29.966MB)<br>
> > >>> >> > + cleaning: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1<br>
> > >>> >> > reporting: tools/rtems-binutils-2.34.cfg -> sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1.txt<br>
> > >>> >> > reporting: tools/rtems-binutils-2.34.cfg -> sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1.xml<br>
> > >>> >> > config: tools/rtems-gcc-7.5.0-newlib-fbaa096.cfg<br>
> > >>> >> > - package: sparc-rtems5-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1<br>
> > >>> >> > - building: sparc-rtems5-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1<br>
> > >>> >> > + package: sparc-rtems6-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1<br>
> > >>> >> > + building: sparc-rtems6-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1<br>
> > >>> >> > ....<br>
> > >>> >> > Build Sizes: usage: 5.684GB total: 1.112GB (sources: 143.803MB, patches: 21.348KB, installed 995.188MB)<br>
> > >>> >> > Build Set: Time 0:21:35.626294<br>
> > >>> >><br>
> > >>> >> Did you run the command and capture the sample output, or do you edit<br>
> > >>> >> the sample output manually?<br>
> > >>> >><br>
> > >>> >> It would be better to copy-paste the actual sample output. Making this<br>
> > >>> >> version change update automatic could be a nice small scripting<br>
> > >>> >> exercise.<br>
> > >>> >><br>
> > >>> >> > @@ -55,7 +55,7 @@ works with the following command:<br>
> > >>> >> ><br>
> > >>> >> > .. code-block:: none<br>
> > >>> >> ><br>
> > >>> >> > - $HOME/quick-start/rtems/5/bin/sparc-rtems5-gcc --version<br>
> > >>> >> > + $HOME/quick-start/rtems/6/bin/sparc-rtems6-gcc --version<br>
> > >>> >> ><br>
> > >>> >> > This command should output something like below. The version informtion helps<br>
> > >>> >> Unrelated, but can you fix this typo: information<br>
> > >>> >><br>
> > >>> >> > you to identify the exact sources used to build the cross compiler of your<br>
> > >>> >> > @@ -69,8 +69,8 @@ source code used.<br>
> > >>> >> ><br>
> > >>> >> > .. code-block:: none<br>
> > >>> >> ><br>
> > >>> >> > - sparc-rtems5-gcc (GCC) 7.5.0 20191114 (RTEMS 5, RSB 5.1.0, Newlib fbaa096)<br>
> > >>> >> > - Copyright (C) 2017 Free Software Foundation, Inc.<br>
> > >>> >> > + sparc-rtems6-gcc (GCC) 10.2.1 20210309 (RTEMS 6, RSB 5e449fb5c2cb6812a238f9f9764fd339cbbf05c2, Newlib d10d0d9)<br>
> > >>> >> > + Copyright (C) 2020 Free Software Foundation, Inc.<br>
> > >>> >> > This is free software; see the source for copying conditions. There is NO<br>
> > >>> >> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.<br>
> > >>> >> ><br>
> > >>> >> > --<br>
> > >>> >> > 2.25.1<br>
> > >>> >> ><br>
> > >>> >> > _______________________________________________<br>
> > >>> >> > devel mailing list<br>
> > >>> >> > <a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a><br>
> > >>> >> > <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> > ><br>
> > > _______________________________________________<br>
> > > devel mailing list<br>
> > > <a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a><br>
> > > <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
</blockquote></div>