<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Hello Matthias,</p>
<p>That's certainly not wanted behavior. I checked and it doesn't
happen in our builds. I think your assessment is correct that the
-R flag culprit is introduced in X_LIBS from the builtin autoconf
macros. Digging through the history, it happened in [1], which is
a long time ago. Only removing -R on cross compile probably isn't
correct. We should at least remove it when using a devkit/sysroot.
Maybe the only time we should let it stay is if any of the
explicit --with-x/--with-x-libraries are used?<br>
</p>
<p>/Erik</p>
<p>[1] <a class="moz-txt-link-freetext" href="https://bugs.openjdk.org/browse/JDK-8005855">https://bugs.openjdk.org/browse/JDK-8005855</a><br>
</p>
<div class="moz-cite-prefix">On 8/31/23 06:02, Baesken, Matthias
wrote:<br>
</div>
<blockquote type="cite" cite="mid:AM9PR02MB67704AA2C3666F331B5ED37C93E5A@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-fareast-language:EN-US;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
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, by chance we
noticed that a jdk build on RHEL Linux (ppc64le if that
matters) that uses a devkit puts the devkits folder
into the libsplashscreen.so binary .<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">See those objdump and
ldd output :<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">objdump -x
./lib/libsplashscreen.so | grep PATH<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> RUNPATH
/mydevkitsfolder/devkits/ppc64le-linux-gnu-to-ppc64le-linux-gnu-fedora27-gcc11.3.0/ppc64le-linux-gnu/sysroot/usr/lib64:$ORIGIN<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">ldd
./lib/libsplashscreen.so<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">ldd: warning: you do not
have execution permission for `./lib/libsplashscreen.so'<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">
libX11.so.6 =>
/mydevkitsfolder/devkits/ppc64le-linux-gnu-to-ppc64le-linux-gnu-fedora27-gcc11.3.0/ppc64le-linux-gnu/sysroot/usr/lib64/libX11.so.6
(0x00007fffa3920000)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">
libXext.so.6 =>
/mydevkitsfolder/devkits/ppc64le-linux-gnu-to-ppc64le-linux-gnu-fedora27-gcc11.3.0/ppc64le-linux-gnu/sysroot/usr/lib64/libXext.so.6
(0x00007fffa38e0000)<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"> libz.so.1
=>
/mydevkitsfolder/devkits/ppc64le-linux-gnu-to-ppc64le-linux-gnu-fedora27-gcc11.3.0/ppc64le-linux-gnu/sysroot/usr/lib64/libz.so.1
(0x00007fffa36f0000)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> libc.so.6
=> /lib64/power9/libc.so.6 (0x00007fffa34e0000)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> libjvm.so
=> not found<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">
libxcb.so.1 => /lib64/libxcb.so.1 (0x00007fffa3490000)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">
/lib64/ld64.so.2 (0x00007fffa3be0000)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">
libXau.so.6 => /lib64/libXau.so.6 (0x00007fffa3460000)<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">This looks not really
desired to me , why should the devkit be referenced there
(we do not ship it usually) ?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Looks like it is coming
in via the X_LIBS setting , see
<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-DE">make/autoconf/lib-x11.m4<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"> # Now let autoconf
do it's magic<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"> AC_PATH_X<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"> AC_PATH_XTRA<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="en-DE"> # AC_PATH_XTRA
creates X_LIBS and sometimes adds -R flags. When cross
compiling<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span lang="en-DE"> # this doesn't
make sense so we remove it.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span lang="en-DE"> if test
"x$COMPILE_TYPE" = xcross; then<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"> X_LIBS=`$ECHO
$X_LIBS | $SED 's/-R \{0,1\}[[^ ]]*//g'`<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"> </span><span lang="EN-US">fi<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"> And X_LIBS is used
later on Linux in the build of LIBSPLASHSCREEN .<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Should we filter it
out not only in the cross build but also when building with
the devkit ? Or is there some benefit in having the
devkit referenced ?<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">What is still unclear,
why we do not see it when building on SUSE instead of RHEL
(maybe the linker behaves differently for some reason?) .<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards, Matthias <o:p></o:p></span></p>
</div>
</blockquote>
</body>
</html>