[security-dev 00039]: Re: JDK 7 build 24 is available at the openjdk.java.net website

Brad Wetmore Bradford.Wetmore at Sun.COM
Tue Jan 8 18:43:53 PST 2008

*Moving the discussion to security-dev)

I'm glad Andreas was able to help you resolve your issue while I was on 

There is one more minor issue which came out of this discussion.  I 
included the Release.gmk files too early in my crypto Makefiles, and as 
a result, gnumake by itself will fail because the wrong default target 
is made.

6644659:  Error in default target of make/javax/crypto in OpenJDK build

As a workaround, simply specify the desired target, such as:

     % gnumake all

This won't affect the default OpenJDK builds, as they build "all" by 

Thanks, and Happy New Year.


Arnd-Hendrik Mathias wrote:
> Hi Andreas,
> Andreas Sterbenz wrote:
>> See below output of a rebuild of make/javax/crypto after a previous 
>> build of a fresh clone of the Mercurial jdk repository. If you see 
>> something different, that must be related to your build environment, 
>> e.g. version of make used, out of date binary plugs, etc.
> Since my output looked quite different, it was not really comparable 
> with the correct output you posted. After further examination of the 
> make-/build environment, I found out that the make environment assumes 
> some tools to reside in /usr/bin per default. I found that this can be 
> overwritten by the ALT_USRBIN_PATH variable. However, if tools reside in 
> different directories (/bin /usr/bin ...) setting
> ALT_USRBIN_PATH=                <empty>
> and having the PATH variable set to have all these tools available 
> directly may be the method the most likely to work. In my special case 
> "head" was missing, residing in /bin on my system.

More information about the security-dev mailing list