I've used this thread as an example: https://universeathome.pl/universe/forum_thread.php?id=671

I've istalled Boinc and adjust it so it could run on the 64 bit OS as stated in the thread.
sudo dpkg --add-architecture armhf
sudo apt update
sudo apt install libstdc++6:armhf libgomp1:armhf libboinc7:armhf
sudo reboot

After that I added the cc_config file:
/var/lib/boinc-client/cc_config.xml

Used nano: sudo nano /var/lib/boinc-client/cc_config.xml

-->
<cc_config>
<log_flags>
<task>1</task>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
</log_flags>
<options>
<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
<options>
</cc_config>

Restarted the Boinc-client and it started to run, got tasks, and it started crunching. So, I'am happy.

But in the Notices tab I see these errors:
Notice from BOINC
Unrecognized tag in cc_config.xml: <options>
Sun 11 Sep 2022 14:52:07 CEST

Notice from BOINC
Error in cc_config.xml options
Sun 11 Sep 2022 14:52:07 CEST

Notice from BOINC
Missing end tag in cc_config.xml
Sun 11 Sep 2022 14:52:07 CEST

I've checked and recheked the cc_config file but I can't see anything wrong in compare to the threat I used as an example.

So, I have three questions:
- Did I do something wrong or forgot something?
- Are the errors any effect on how it functions?
- If nessesary: how do I fix this?

I must confess that I'm not having much knowlegde about Linux sort of OS'es.So please respond on a beginners level.

---

What I see that

<options>

you have opened twice, not closed.

---

Krzysztof 'krzyszp' Piszczek

Member of Radioactive@Home team
My Patreon profile
Universe@Home on YT

Thanks for your reply Krzysztof.
I'm not shure what you means by that. Perhaps you can point me out how to "close" it instead of opening it twice?
I did copy the syntax out of the original threat so that must be wrong as well?

---

Blocks are opened with <example> and closed with </example>, with a slash before the identifier.
The problem here would be that the <options> block has the slash missing, when it should get closed.
The source has indeed the same error.
Wrong:

<options>
<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
<options>

Right:

<options>
<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
</options>

This works like the formatting here in the forum: Closing a "code" formatting block, when it hasn't been opened: [/code]

In:

<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
<options>
</cc_config>

should by:

<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
</options>
</cc_config>

---

Krzysztof 'krzyszp' Piszczek

Member of Radioactive@Home team
My Patreon profile
Universe@Home on YT

Aha, thank you very much.
That did the trick. :-)

Thank you all for the advice. I've learned somthing today.

thx, that hint does the solution for me too :-)

cu, stephan

thx, that hint does the solution for me too :-)

cu, stephan

Hi, Guys. Wow, that is so weird. I can see the logic of needing </options>
to clse out <options> but my /var/lib/boinc-client/cc_config.xml still remains:

<options>
<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
<options>

and it's been running boinc on my pi-400 for several weeks now, across
multiple reboots.

-Mike

It should be complaining and being ignored. Just don't wake the beast in your case I guess.

There is a great website for checking the syntax of XML files for correct formatting that shows any errors in a simple copy and paste interface that I think should be used by anyone crafting a BOINC XML file. Prevents stupid typos and omissions.

https://www.xmlvalidation.com/index.php

---

A proud member of the OFA (Old Farts Association)