Please provide verbose output of compiler commands when building code with C/C++ libs #45724
Labels
FrozenDueToAge
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?darwin/amd64
go env
OutputWhat did you do?
Any code which requires C-binding, e.g. in my case I was trying to build against opencv and libtorch libraries.
What did you expect to see?
The
go build
command provides no output of how underlying C/C++ build is performed. When I provide-v
verbose flag I expect to see a full output of underlyinggcc/g++/clang++
commands which were called from thego build
. Otherwise it is extremely hard to understand details of the build.What did you see instead?
Here is a simple example:
This output tells me that I'm missing opencv2 includes. Ok, I can supply the include dirs, e.g.
From this output I have no clue how build was done, which compiler commands were issued, etc. Here I expect to see something like (which I was able to grab of
ps
output during my build):Please provide full verbose output of underlying
c/c++
compiler commands issued bygo build
. This will allows developers save time to debug the issues with C binding libraries and know exactly how to reproduce the build issues. For instance, I can get the compiler commands fromps
output command, but it requires lots of jumping between windows, but still does not guarantee that I can catch exact commands which fails. We need to see fullc/c++/clang
output including errors, warnings, etc., as we usually do when compiling C/C++ code. I suggest to capturego build
stdout/stderr output and allow developers to see these outputs duringgo build
command.The text was updated successfully, but these errors were encountered: