Ticket #11332 (closed defect: wontfix)

Opened 2 years ago

Last modified 2 years ago

unable to build on sabotage linux (using musl libc) due to use of binary program "kmk_sed"

Reported by: John.Spencer Owned by:
Priority: major Component: installer
Version: VirtualBox 4.2.6 Keywords:
Cc: Guest type: other
Host type: other


Checking for libpng: found version 1.5.11, OK. ./configure: line 2565: /src/build/virtualbox/VirtualBox-4.2.6/kBuild/bin/linux.amd64/kmk_sed: not found

kmk_sed is a binary program linked against glibc.

the "not found" error message stems from the dynlinker which tries to open the DT_INTERP from glibc:

$ readelf -a /src/build/virtualbox/VirtualBox-4.2.6/kBuild/bin/linux.amd64/kmk_sed | grep -i INTERP

[ 1] .interp PROGBITS 0000000000400200 00000200 INTERP 0x0000000000000200 0x0000000000400200 0x0000000000400200

[Requesting program interpreter: /lib64/]

also note that neither the glibc dynlinker nor /lib64 exists.

this is the first program i've encountered in my entire life that executes it own binary programs during *SOURCE CODE* compilation.

this is completely unportable. please change your build scripts to use POSIX sed instead of your own weird binary thing.

Change History

comment:1 Changed 2 years ago by aeichner

The binary is part of the VirtualBox cross platform build system. They are provided for convenience for users wanting to compile VBox from source. If they don't work on your system just compile them yourself (The source can be found here ) and put them in your PATH environment. We will not change our buildsystem to use tools on the hostplatform because they sometimes don't work in a cross platform manner, so we rely on our own tools with a well defined behavior. Closing as won't fix.

comment:2 Changed 2 years ago by aeichner

  • Status changed from new to closed
  • Resolution set to wontfix

comment:3 Changed 2 years ago by frank

I have deleted the last insulting comment.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use