On Fri, Jul 11, 2014 at 1:56 PM, David Holmes <david.hol...@oracle.com> wrote:
> On 11/07/2014 9:36 PM, pointo1d wrote:
>>
>> TFT David ,
>>
>> On 11/07/14 06:01, David Holmes wrote:
>>>
>>> On 11/07/2014 2:09 AM, pointo1d wrote:
>>>>
>>>> <snip>
>>>
>>>
>>> Check earlier in the build log to see why the corba classes.jar didn't
>>> get built.
>>
>>
>> The corba fails to build because it seemingly can't find the most basic
>> things ...
>>
>> ## Starting corba
>> Compiling 6 files for BUILD_LOGUTIL
>>
>> /home/dpointo8/work/repos/Mercurial/ojdk8.datum/corba/src/share/classes/com/sun/tools/corba/se/logutil/InputException.java:30:
>> error: cannot access Object
>> public class InputException {
>> ^
>> class file for java.lang.Object not found
>>
>> I do wonder if the image being specified in the --with-import-hotspot &
>> --with-boot-jdk options is lacking in some respect ... like the language
>> fundamentals perhaps ? Is there a definition of the expected composition
>> of any external hotspot &/or boot JDK ?
>
>
> I don't know what the hotspot import requirements are as I've never used it.
> The boot JDK has to be a full JDK - the sanity check should ensure it meets
> the minimum version needed for what is being built.
>
This is the following problem:
"8026964: Building with an IBM J9 boot jdk requires special settings
for BOOT_RTJAR"
I had a patch for it:
http://cr.openjdk.java.net/~simonis/webrevs/8026964.v2/
http://cr.openjdk.java.net/~simonis/webrevs/8026964.jdk/
which wasn't accepted because it led to problems with the MinGW build
and I didn't had time to investigate that problem further (see this
mail thread:
http://mail.openjdk.java.net/pipermail/build-dev/2013-November/thread.html#11108)
I'm ready to resume working on it if there's a real need.
>>>
>>>> <snip>
>>>
>>>
>>> This probably relates to the assumption that !OPENJDK == Oracle JDK.
>>> Do your builds set OPENJDK or not? There was a long thread on this not
>>> that long ago.
>>
>>
>> They [my builds] didn't explicitly set OPENJDK, but having now done so
>> (to both 'true' and then 'false' in turn), the outcome is unchanged.
>
>
> Hmmm - if you don't set OPENJDK it will assume Oracle JDK behaviour but you
> won't have the Oracle specific files so weird things should happen.
>
> BTW your build should default to OPENJDK unless you have to have defined
> things that look like the Oracle closed repos.
>
> Can you back up a step and simply verify if you can build OPENJDK using only
> OpenJDK sources?
>
> David
>
>
>>>
>>> David
>>>
>>>> TIA ,
>>>>
>>
>> --
>> Dave Pointon FIAP MBCS - Contractor engaged by IBM
>>
>> Now I saw, tho' too late, the folly of beginning a work before we count
>> the cost and before we we judge rightly of our strength to go thro' with it
>> - Robinson Crusoe
>>
>
