Dead links cause a message in the form of ERROR: Can't access file [dead link path] to be printed which doesn't make too much sense because it's not an error in terms of a virus scan, it's just an unimportant state of an unimportant part of the filesystem, it's a debugging or trace message.
Example:
> cd /tmp/test/
> ln -s -T /inexisting file
> sudo clamdscan --fdpass --multiscan /tmp/test/
ERROR: Can't access file /tmp/test/file
----------- SCAN SUMMARY -----------
Infected files: 0
Total errors: 1
Time: 0.000 sec (0 m 0 s)
Can I avoid this message with a built-in option of clamd? It doesn't prevent clamd from working well, but clutters up the output. I checked them and none appears convincing, but they're not overly clear in names and the configuration files wasn't commented. It's not worth to figure this out in detail or filtering the output.
Removing the links is work intensive (not only once, but every time e.g. a build process creates such links) and doesn't lead to a deterministic suppression of the issue. It's a valid temporary workaround.
I'm using 0.99.2+dfsg-2ubuntu2 on Ubuntu 16.10.