AIX class library changes - update and questions
Hi, I usually prefer _AIX to AIX because the former is an predefined compiler macro in xlc and therefore always works. Same reason for __linux__and __sun and so on. But I admit this clashes with what Oracle is doing in their make files... Kind Regards, Thomas
Hi Steve,
yes, in both cases we would follow your approach.
In the hotspot code we anyways (mostly) use AIX without underscore, and we will adapt the jdk accordingly.
Also we should use the Open Source packages, and the standard path settings.
Yours, Goetz & Volker
-----Original Message----- From: ppc-aix-port-dev-bounces at openjdk.java.net [mailto:ppc-aix-port-dev-bounces at openjdk.java.net] On Behalf Of Steve Poole Sent: Montag, 9. Juli 2012 09:59 To: AIX class library changes - update and questions Subject: AIX class library changes - update and questions
Hi all - quick update and some questions.
I've been going through the IBM and SAP changes and building them incrementally. I'm not finished yet but I wanted to float a couple of questions.
1 - use of #ifdef _AIX versus #ifdef AIX. SAP uses "_AIX" while IBM uses "AIX". For other platforms we see "__linux__" or "__solaris__"
Any preference on _AIX vs AIX or something else? Currently I'm using AIX and changing any _AIX I find.
2 - We are relying on Open Source packages for some of the tools (find for instance). I'd like to make sure we are all using the same set of packages and that their installed location is the same - OR - we just agree that PATH has to be set correctly first :-)
A concrete example: I noticed that SAP's common/Defs-aix.gmk file has a hard coded reference to find being in '/usr/local/bin' If you use the oss4aix packages then the relevant RPM installs find into '/opt/freeware/bin'
Any thoughts on this ?
participants (1)
-
Thomas Stüfe