Re: BSP Nomenclature

--===============3786495728352225163==
Content-Type: multipart/alternative; boundary="000000000000b5030a062d06a02f"

--000000000000b5030a062d06a02f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 31, 2025 at 2:11=E2=80=AFPM Robert W <[email protected]> wrote:

> > This sounds like you might be using the BSP build sets in the RSB. It
> might
> > be better for you to build just the tools with the bset 6/rtems-m68k an=
d
> then
> > build and test BSPs individually. That way you can test, tweak, debug,
> test,
> > etc each BSP without having to rebuild the tools.
> >
> > The tools do not need to change between builds of BSPs within the same
> > architecture which is why the BSP bsets are good for production
> deployment
> > but can be awkward for testing.
> >
> > --joel
>
>
>
> From "
> https://ftp.rtems.org/pub/rtems/releases/5/5.3/#quick-guide-to-building"
>
> "
> .
> .
> .
> To build the tools for the ARM architecture:
>
> ../source-builder/sb-set-builder \
>   --prefix=3D$HOME/development/rtems/5.3 \
>   5/rtems-arm
> "
>
> This *exact* ( used this line out of the manual for this target) line
> fails with:
>
> "
> .
> .
>
> building: expat-2.1.0-x86_64-linux-gnu-1
> sizes: expat-2.1.0-x86_64-linux-gnu-1: 7.459MB (installed: 1.417MB)
> cleaning: expat-2.1.0-x86_64-linux-gnu-1
> reporting: devel/expat-2.1.0-1.cfg -> expat-2.1.0-x86_64-linux-gnu-1.txt
> reporting: devel/expat-2.1.0-1.cfg -> expat-2.1.0-x86_64-linux-gnu-1.xml
> config: tools/rtems-gdb-9.1-1.cfg
> error: shell macro failed:
>
> /usr/local/packages/ee/rtems/rtems.20250125.2015.rtems52/rtems-source-bui=
lder-5.2/source-builder/sb/rtems-build-dep
> -c gcc  -l : 2: error: no library (-l) provided
> Build FAILED
> Build Set: Time 0:00:23.866886
> Build FAILED
> "
> **Please note that this sequence successfully builds "automake" and
> "autoconf" before encountering the error building gdb
>
> Is this not the right way to build the tools?
> I'm not able to find any other instructions for building compiler tools.
>

I am pretty sure 5.3 is still referencing URLs that do not exist since we
switched
to Gitlab. The 5 branches should be OK. We are discussing cutting a 5.4 but
it was
second to getting 6.1 out.

6.1 is out and would be a better starting point.

Also you can add --log=3DFILE and maybe even --trace to see what was tried
but
it looks like it didn't find a library it needed (no idea which or why) and
the name on
the -l argument expanded to nothing.

--joel

>
> Help appreciated, Thanks.
>
> Robert W.
>

--000000000000b5030a062d06a02f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 31,=
 2025 at 2:11=E2=80=AFPM Robert W &lt;<a href=3D"mailto:[email protected]">r=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex">&gt; This sounds like you might be using the BSP build sets =
in the RSB. It might<br>
&gt; be better for you to build just the tools with the bset 6/rtems-m68k a=
nd then<br>
&gt; build and test BSPs individually. That way you can test, tweak, debug,=
 test,<br>
&gt; etc each BSP without having to rebuild the tools.<br>
&gt;<br>
&gt; The tools do not need to change between builds of BSPs within the same=
<br>
&gt; architecture which is why the BSP bsets are good for production deploy=
ment<br>
&gt; but can be awkward for testing.<br>
&gt;<br>
&gt; --joel<br>
<br>
<br>
<br>
From &quot;<a href=3D"https://ftp.rtems.org/pub/rtems/releases/5/5.3/#quick=
-guide-to-building" rel=3D"noreferrer" target=3D"_blank">https://ftp.rtems.=
org/pub/rtems/releases/5/5.3/#quick-guide-to-building</a>&quot;<br>
<br>
&quot;<br>
.<br>
.<br>
.<br>
To build the tools for the ARM architecture:<br>
<br>
../source-builder/sb-set-builder \<br>
=C2=A0 --prefix=3D$HOME/development/rtems/5.3 \<br>
=C2=A0 5/rtems-arm<br>
&quot;<br>
<br>
This *exact* ( used this line out of the manual for this target) line<br>
fails with:<br>
<br>
&quot;<br>
.<br>
.<br>
<br>
building: expat-2.1.0-x86_64-linux-gnu-1<br>
sizes: expat-2.1.0-x86_64-linux-gnu-1: 7.459MB (installed: 1.417MB)<br>
cleaning: expat-2.1.0-x86_64-linux-gnu-1<br>
reporting: devel/expat-2.1.0-1.cfg -&gt; expat-2.1.0-x86_64-linux-gnu-1.txt=
<br>
reporting: devel/expat-2.1.0-1.cfg -&gt; expat-2.1.0-x86_64-linux-gnu-1.xml=
<br>
config: tools/rtems-gdb-9.1-1.cfg<br>
error: shell macro failed:<br>
/usr/local/packages/ee/rtems/rtems.20250125.2015.rtems52/rtems-source-build=
er-5.2/source-builder/sb/rtems-build-dep<br>
-c gcc=C2=A0 -l : 2: error: no library (-l) provided<br>
Build FAILED<br>
Build Set: Time 0:00:23.866886<br>
Build FAILED<br>
&quot;<br>
**Please note that this sequence successfully builds &quot;automake&quot; a=
nd<br>
&quot;autoconf&quot; before encountering the error building gdb<br>
<br>
Is this not the right way to build the tools?<br>
I&#39;m not able to find any other instructions for building compiler tools=
.<br></blockquote><div><br></div><div>I am pretty sure 5.3 is still referen=
cing URLs that do not exist since we switched</div><div>to Gitlab. The 5 br=
anches should be OK. We are discussing cutting a 5.4 but it was</div><div>s=
econd to getting 6.1 out.</div><div><br></div><div>6.1 is out and would be =
a better starting point.</div><div><br></div><div>Also you can add --log=3D=
FILE and maybe even --trace to see what was tried but=C2=A0</div><div>it lo=
oks like it didn&#39;t find a library it needed (no idea which or why) and =
the name on</div><div>the -l argument expanded to nothing.</div><div><br></=
div><div>--joel=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
<br>
Help appreciated, Thanks.<br>
<br>
Robert W.<br>
</blockquote></div></div>

--000000000000b5030a062d06a02f--

--===============3786495728352225163==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
users mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/users
--===============3786495728352225163==--