[MacPorts] #64174: gvisor-tap-vsock: file was built for unsupported file format ( 0x7F 0x45 0x4C 0x46 0x02 0x01 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64)

[MacPorts]

#64174: gvisor-tap-vsock: file was built for unsupported file format ( 0x7F 0x45
0x4C 0x46 0x02 0x01 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 )
which is not the architecture being linked (x86_64)
-------------------------------+----------------------
  Reporter:  ryandesign        |      Owner:  judaew
      Type:  defect            |     Status:  assigned
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.7.1
Resolution:                    |   Keywords:  sierra
      Port:  gvisor-tap-vsock  |
-------------------------------+----------------------

Comment (by ryandesign):

 The portfile asks to build the target `build`, and the Makefile says:

 {{{
 .PHONY: build
 build: gvproxy qemu-wrapper vm

 .PHONY: gvproxy
 gvproxy:
         go build $(LDFLAGS) -o bin/gvproxy ./cmd/gvproxy

 .PHONY: qemu-wrapper
 qemu-wrapper:
         go build $(LDFLAGS) -o bin/qemu-wrapper ./cmd/qemu-wrapper

 .PHONY: vm
 vm:
         GOOS=linux CGO_ENABLED=0 go build $(LDFLAGS) -o bin/vm ./cmd/vm
 }}}

 But then the port's destroot phase only installs `gvproxy`. So there
 doesn't seem to be any reason to build the qemu-wrapper and vm targets,
 the latter of which seems to be the source of the problem. Should the port
 be changed to use build target gvproxy instead?

-- 
Ticket URL: <https://trac.macports.org/ticket/64174#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS