Weird thing is that I think virustotal is backed up by Google (not 100%
sure) so it is curious they don't push on a more decent recognition, or
provide some detection guidelines. Staying still that the blame is on AV
makers, of course.
On Fri, May 13, 2022, 21:59 Amnon wrote:
> My workaround is
I use Windows and Kaspersky. I build Go from source. I don't have such
problem.
On Saturday, May 14, 2022 at 2:59:09 AM UTC+7 Amnon wrote:
> My workaround is not to use Windows.
> And not to use anti-virus programs that thing all Go programs are viruses.
>
> On Friday, 13 May 2022 at 16:21:31 U
My workaround is not to use Windows.
And not to use anti-virus programs that thing all Go programs are viruses.
On Friday, 13 May 2022 at 16:21:31 UTC+1 drro...@gmail.com wrote:
> My work around is to compile using -ldflags="-s -w"
>
> This has worked for the cases when my files make Windows unh
My work around is to compile using -ldflags="-s -w"
This has worked for the cases when my files make Windows unhappy. I
reported it as a bug to Microsoft months ago; I see that they got right on
it.
--rob solomon
On Wednesday, May 11, 2022 at 11:50:20 AM UTC-4 Rusco wrote:
> Regarding: "co
Regarding: "compile a simple helloworld main ...":
My workaround is to insert a
import "C"
among the other imports. It somehow alters the structure of the binary
created and my av no more recognizes the binary. This is actually something
which never happened when I am doing some Rust work.
