-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AIX 7.3 system #3142
Comments
Machine is installed with xlc13 and xlc16. The rest needs to be done using playbook (@sxa @Haroon-Khel ) Further, made a PR to rename the system as |
Thanks Michael! |
Thanks Michael, I will run the playbook on the machine |
An error when using Yum
Investigating a solution |
The thread in https://community.ibm.com/community/user/power/discussion/yum-broken-after-aix-73-upgrade suggests yum is no longer supported on AIX7.3, dnf is recommended |
dnf is installed, packages updated without error. Machine is online at https://ci.adoptium.net/computer/test-osuosl-aix73-ppc64-1/ |
Will need to add the dnf install steps to the playbooks for aix7.3 machines |
aqa test pipeline job running on test-osuosl-aix73-ppc64-1 https://ci.adoptium.net/job/AQA_Test_Pipeline/155/console |
Added the From #1006 (comment) I take it we want it to use |
These kind of errors are why I was never a fan of the AIX Toolbox. If you can file a PMR with IBM AIXToolbox team - I would do that. They need to fix this rather than potentially breaking things - continually - when you want to use their tools. imho: they should have the libpath - when it deviates - in the executable (dump -H shows the built-in libpath). |
Looks like the LIBPATH value java uses can be overidden with the
|
IMHO: they are asking for issues by putting their libraries first, rather than /usr/lib.
ALSO: if the default LIBPATH includes …/jdk-17*/… stuff, and using the -Djava.library.path argument erases all of those – I would expect different problems down the road – else – why bother with the /usr/jdk-17.0.7+7/lib/server:/usr/jdk-17.0.7+7/lib:/usr/jdk-17.0.7+7/../lib: bits in the first place – OR – maybe that is the bug – the wrong compiler, read linker, arguments putting unneeded Library paths.
My gut feeling is that using -Djava.library.path is treating a symptom, not resolving a problem.
***@***.***>
Michael Felt
Mobile +31 (0)6 5184 4181
Email ***@***.***
From: Haroon Khel ***@***.***>
Sent: Friday, August 11, 2023 5:07 PM
To: adoptium/infrastructure ***@***.***>
Cc: Michael Felt ***@***.***>; Author ***@***.***>
Subject: Re: [adoptium/infrastructure] AIX 7.3 system (Issue #3142)
Looks like the LIBPATH value java uses can be overidden with the -Djava.library.path parameter . Using the simple java class below
public class Main {
public static void main(String[] args) {
System.out.println(System.getProperty("java.library.path"));
}
}
***@***.***:[/home/jenkins]/usr/java17_64/bin/java Main
/usr/jdk-17.0.7+7/lib/server:/usr/jdk-17.0.7+7/lib:/usr/jdk-17.0.7+7/../lib:/lib:/usr/lib
***@***.***:[/home/jenkins]/usr/java17_64/bin/java -Djava.library.path="/opt/freeware/lib/" Main
/opt/freeware/lib/
—
Reply to this email directly, view it on GitHub <#3142 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSZR5M2LX23SNI6RZZBTL3XUZC7ZANCNFSM6AAAAAA22AS67Q> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/ACSZR5LOVVOJFCFFU2CBTQ3XUZC7ZA5CNFSM6AAAAAA22AS67SWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTD2WFKE.gif> Message ID: ***@***.*** ***@***.***> >
|
Do we know how to move this forward? It would be good to have an AIX 7.3 machine in the jenkins set for testing. We also have the system in #3208 which is AIX7.3+xlc17 which we need to get set up, but we should aim to get both working as usable systems. |
@Haroon-Khel Ref earlier conversation the above comments suggest the machine has not yet made it to being usable because there are issues with |
Yes I believe that is still an outstanding issue |
Downgrading to |
Looks like it still has issues - maybe 32/64-bit related?
Almost certainly a 32-bit libbz2 and trying to load a 64-bit libgcc_s, although an |
I'm done for now - someone else can take over this investigation and comparison with a working system :-) There is a /usr/lib64/libbz2.a that should correctly work with a 64-bit libgcc_s.a but it's not the one that's being picked up. |
Noting that the 7.3 machine which is live in jenkins is not currently capable of running the smoke tests for JDK head:
|
Please put the name of the software product (and affected platforms if relevant) in the title of this issue
Details:
As AIX 7.1 is now retired (see #3030) I am creating this issue for tracking any issues that come during the running of the playbook for the first time on AIX 7.3 (@Haroon-Khel - I hope you can do this).
The text was updated successfully, but these errors were encountered: