<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:sebastian.huber@embedded-brains.de">Sebastian Huber</a><br><b>Sent: </b>Tuesday, October 18, 2022 11:15 AM<br><b>To: </b><a href="mailto:alan.cudmore@gmail.com">Alan Cudmore</a>; <a href="mailto:joel@rtems.org">joel@rtems.org</a><br><b>Cc: </b><a href="mailto:devel@rtems.org">rtems-devel@rtems.org</a><br><b>Subject: </b>Re: Ping on ticket 4728 + patch</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 18/10/2022 16:36, Alan Cudmore wrote:</p><p class=MsoNormal>> On Tue, Oct 18, 2022 at 9:55 AM Joel Sherrill<joel@rtems.org> wrote:</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> On Tue, Oct 18, 2022 at 8:44 AM Alan Cudmore<alan.cudmore@gmail.com> wrote:</p><p class=MsoNormal>>>> The log does have the error, and I get it when building by hand too:</p><p class=MsoNormal>>>> start.o: in function `.L0 ':</p><p class=MsoNormal>>>> /home/alan/rtems/test-build/rtems-tmp/build/riscv/rv32imafdc/../../../bsps/riscv/shared/start/start.S:86:(.bsp_start_text+0x5c):</p><p class=MsoNormal>>>> relocation truncated to fit: R_RISCV_GPREL_I against symbol</p><p class=MsoNormal>>>> `bsp_section_bss_size' defined in*ABS* section in</p><p class=MsoNormal>>>> /home/alan/rtems/test-build/rtems-tmp/build/riscv/rv32imafdc/testsuites/samples/minimum.exe</p><p class=MsoNormal>>>> collect2: error: ld returned 1 exit status</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> Hmmm.. that's weird. You should never get a truncation error linking minimum.exe.</p><p class=MsoNormal>>> It should always fit within the BSP's memory and not have any issues with branches</p><p class=MsoNormal>>> or calls needing fixup.</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> Unless the wrong type of branch/jump/call instruction is used at start.S:86, I have</p><p class=MsoNormal>>> no idea.If it's a form that assumes a short distance to the destination but is going</p><p class=MsoNormal>>> to a symbol outside start.S and thus could be further.</p><p class=MsoNormal>> Also, 6 of the samples such as hello.exe link without error.</p><p class=MsoNormal>> The rv32imafdc BSP variant does not have CPU_CFLAGS.</p><p class=MsoNormal>> rv32imafd links fine and has specific CPU_CFLAGS, rv32imafdc does not</p><p class=MsoNormal>> have the flags.</p><p class=MsoNormal>> (I'll research the gcc defaults and architecture differences next..)</p><p class=MsoNormal>> </p><p class=MsoNormal>> I get a similar error on the frdme310arty BSP but only on a specific</p><p class=MsoNormal>> POSIX testsuite executable:</p><p class=MsoNormal>> </p><p class=MsoNormal>> start.o: in function `.L0 ':</p><p class=MsoNormal>> </p><p class=MsoNormal>> /home/alan/rtems/test-build/rtems-tmp/build/riscv/frdme310arty/../../../bsps/riscv/shared/start/start.S:86:(.bsp_start_text+0x28):</p><p class=MsoNormal>> relocation truncated to fit: R_RISCV_GPREL_I against symbol</p><p class=MsoNormal>> `bsp_section_bss_size' defined in*ABS* section in</p><p class=MsoNormal>> /home/alan/rtems/test-build/rtems-tmp/build/riscv/frdme310arty/testsuites/validation/ts-validation-io-kernel.exe</p><p class=MsoNormal>> </p><p class=MsoNormal>> collect2: error: ld returned 1 exit status</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>My off hand guess is that this is a tool chain issue on certain host </p><p class=MsoNormal>systems. For example, I never got this error on our OpenSUSE machines.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I can set up a OpenSUSE virtual machine and try it. I noticed the RSB documentation does not have a set of packages for OpenSUSE – I could send a docs patch after a successful build. What release do you use? Do you have a list of packages to install?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Alan </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-- </p><p class=MsoNormal>embedded brains GmbH</p><p class=MsoNormal>Herr Sebastian HUBER</p><p class=MsoNormal>Dornierstr. 4</p><p class=MsoNormal>82178 Puchheim</p><p class=MsoNormal>Germany</p><p class=MsoNormal>email: sebastian.huber@embedded-brains.de</p><p class=MsoNormal>phone: +49-89-18 94 741 - 16</p><p class=MsoNormal>fax: +49-89-18 94 741 - 08</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Registergericht: Amtsgericht München</p><p class=MsoNormal>Registernummer: HRB 157899</p><p class=MsoNormal>Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler</p><p class=MsoNormal>Unsere Datenschutzerklärung finden Sie hier:</p><p class=MsoNormal>https://embedded-brains.de/datenschutzerklaerung/</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>