Determining golang build output differences between upstream and nixpkg

Hello,
I’m trying to determine why a nixpkg produces a much larger compiled binary compared to when I download the upstream golang package and build it myself.

I’m instantiating nix build like so:
nix build -v --rebuild -L "nixpkgs#the_pkg_i_am_inspecting"
and I only see output messages like this:

the_pkg_i_am_inspecting> source root is source
the_pkg_i_am_inspecting> Running phase: patchPhase
the_pkg_i_am_inspecting> Running phase: updateAutotoolsGnuConfigScriptsPhase
the_pkg_i_am_inspecting> Running phase: configurePhase
the_pkg_i_am_inspecting> Running phase: buildPhase

what I really want to look at is at least the output of make, is there a way to do this with the current tooling?