<p>Yes, this particular warning can be ignored. The given file name is of a system dependency and so there is nothing that can be done about it except to wait for the boost project to fix the error and publish a fix that you can apply to your system.</p>
<p>You can suppress these warnings by configuring with <code>--enable-suppress-external-warnings</code>.</p>

CC BY-SA 4.0
2022-08-25T19:04:45.850Z
This should be on the build documentation, so many warnings obscure the build process
Bitcoin_1o1
CC BY-SA 4.0
2022-07-07T03:51:05.477Z
2022-07-07T03:51:05.477Z
Ava Chow
<p>When I build Bitcoin Core on MacOS I get a number of &quot;overriding a member function&quot; Boost warnings:</p>
<p>e.g.</p>
<pre><code>/usr/local/include/boost/signals2/connection.hpp:212:34: warning: 'release_slot' overrides a member function but is not marked 'override' [-Wsuggest-override]
</code></pre>
<p>Should these be addressed in future or are they entirely harmless and safe to ignore?</p>

<bitcoin-core-development><compiling>
Should these Bitcoin Core build warnings be addressed or are they entirely harmless?
Michael Folkson
# Should these Bitcoin Core build warnings be addressed or are they entirely harmless?

(Asked by: username_0 on 2022-07-06)

When I build Bitcoin Core on MacOS I get a number of "overriding a member function" Boost warnings:

e.g.

```
/usr/local/include/boost/signals2/connection.hpp:212:34: warning: 'release_slot' overrides a member function but is not marked 'override' [-Wsuggest-override]

```

Should these be addressed in future or are they entirely harmless and safe to ignore?

**Tags:** bitcoin-core-development, compiling


---

## 1 answers

### Answer by username_1 on 2022-07-07. Score: 3 | Accepted answer

Yes, this particular warning can be ignored. The given file name is of a system dependency and so there is nothing that can be done about it except to wait for the boost project to fix the error and publish a fix that you can apply to your system.

You can suppress these warnings by configuring with `--enable-suppress-external-warnings`.

> **Comments:**
> **username_2**: This should be on the build documentation, so many warnings obscure the build process  

---

