On 2024-10-28 13:39, Baesken, Matthias wrote:
Hello, I wanted to try the hsdis build (on Linux x86_64) .
After no success my system binutils, I downloaded the sources and
used these configure options :
--with-hsdis=binutils
--with-binutils-src=/mydir/binutils/binutils-2.42.90
The configure part does not complain, and seems the binutils are built.
But no hsdis shared lib shows up after the jdk build is over.
Then I found the --enable-hsdis-bundling configure flag and when
adding it, the hsdis build seems to work, the file
./images/jdk/lib/hsdis-amd64.so is present after the build.
Should we maybe check for --enable-hsdis-bundling or warn/fail
in case it is not set together with the --with-hsdis ?
The reason that the bundling needs to be enabled separately is that
there might be legal problems with bundling the hadis library,
specifically if it is built with the binutils backend. Basically, this
is not legal advice, yadayada, but you are allowed to build, but not
distribute, such a library. By explicitly adding the
--enable-hsdis-bundling flag, you acknowledge that you know what you are
doing.
You can build the hsdis library separately without the bundling using
`make hsdis`, so bundling is not required.
Another issue on my SUSE Linux box was that libopcodes.a was not
detected correctly when using a pre-built binutils dir. The folder
lib was taking but this one was in lib64 .
If you believe this to be a bug, please open a JBS issue.
/Magnus
