<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 2024-10-28 13:39, Baesken, Matthias wrote:<br>
<blockquote type="cite" cite="mid:AM9PR02MB6770AB6FEC0AACA614413B3B934A2@AM9PR02MB6770.eurprd02.prod.outlook.com">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
mso-fareast-language:EN-US;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hello, I wanted to try
the hsdis build (on Linux x86_64) .<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">After no success my
system binutils, I downloaded the sources and used these
configure options :<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> --with-hsdis=binutils
--with-binutils-src=/mydir/binutils/binutils-2.42.90<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The configure part does
not complain, and seems the binutils are built.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">But no hsdis shared lib
shows up after the jdk build is over.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Should we maybe check
for --enable-hsdis-bundling or warn/fail in case it
is not set together with the --with-hsdis ?</span></p>
</div>
</blockquote>
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 <span lang="EN-US">--enable-hsdis-bundling flag, you acknowledge that
you know what you are doing.</span>
<p><span lang="EN-US">You can build the hsdis library separately
without the bundling using `make hsdis`, so bundling is not
required.</span></p>
<blockquote type="cite" cite="mid:AM9PR02MB6770AB6FEC0AACA614413B3B934A2@AM9PR02MB6770.eurprd02.prod.outlook.com">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p>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 .</span></p>
</div>
</blockquote>
<p>If you believe this to be a bug, please open a JBS issue.</p>
<p>/Magnus<br>
</p>
</body>
</html>