Hi

Magnus Ihse Bursie magnus.ihse.bursie at oracle.com
Fri Dec 18 13:55:21 UTC 2015


Hi,

I just subscribed to be in the loop of any build issues for this new 
port, and to keep an eye on you so any changes done to the build system 
is acceptable for a future inclusion in the mailine. ;-)

I read some of the mails from the archive, and just wanted to comment on 
a few things there:

1) Instead of writing "configure --build=aarch64-unknown-linux-gnu 
--host=aarch32-linux-gnueabihf --target=aarch32-linux-gnueabihf " you 
can just write "configure --openjdk-target=aarch32-linux-gnueabihf" for 
brevity.

2) If you happened to get the full jcheck requiring a JBS bug number, 
then you might as well request having the hgupdater hook as well. I just 
looked at JDK-8144905 (since it was reported on the build system), and 
just found out that it had actually been fixed. The hgupdated will 
automatically close bugs when a a changeset mentioning that bug is 
committed. It's quite convenient, if you are really tracking tasks to be 
done using the JIRA.

Also, perhaps you could tag aarch32 bugs with an approriate label, e.g. 
"aarch32"? It's much easier to see tags (labels) than the environment field.

/Magnus


More information about the aarch32-port-dev mailing list