PROCESSOR_IDENTIFIER: command not found

[Kelly O'Hair]

On Jun 6, 2010, at 4:20 PM, cowwoc wrote:

>
> Hi,
>
> I'm trying to build OpenJDK under Windows7 64-bit with Visual Studio  
> 2010.
> When I run jdk_generic_profile.sh I get:
>
> /cygdrive/c/Users/Gili/Documents/jdk7/jdk7/jdk/make/ 
> jdk_generic_profile.sh:
> line
> 177: PROCESSOR_IDENTIFIER: command not found
>
> I am using GNU Make 3.81 for now because I am unable to find a  
> working copy
> of make 3.80 anywhere. The one copy I found gave this error:
>
> /usr/bin/make.exe: error while loading shared libraries:  
> cygintl-2.dll:
> cannot open shared object file: No such file or directory

The CYGWIN make.exe used to have that dependency, then they removed  
the dependency and the
default install of that dll, so if you get a slightly newer make.exe,  
or install the package for cygintl-2.dll, that will work.
Note that we may soon have a requirement of make 3.81, so getting a  
3.81 that works might be better,
I think I'm using the cmake one. The 3.80 has a few minor bugs with  
some of the makefile functions
that people could run into, fixed in 3.81.

The last time I loaded up CYGWIN it was 1.7 something, but 1.5 and 1.7  
behave a little differently.

>
> That being said, I don't think the PROCESSOR_IDENTIFIER error is  
> specific to
> Make. I noticed the makefile contains echo $(PROCESSOR_IDENTIFIER).  
> Running
> this under cygwin's bash gives:
>
>> echo $(PROCESSOR_IDENTIFIER)
> bash: PROCESSOR_IDENTIFIER: command not found
>
> while:
>
>> echo $PROCESSOR_IDENTIFIER
> Intel64 Family 6 Model 15 Stepping 11, GenuineIntel
>
> Where can I get make 3.10 that will work? How do I fix the
> PROCESSOR_IDENTIFIER error?

Makefiles use () or {} on variables, but you cannot leave them out. I  
tend to use () in makefiles
and use {} in shell scripts or shell logic.
Shell scripts use {} or you can leave them out. My mistake for using  
() in the shell script.

-kto

>
> Thank you,
> Gili
> -- 
> View this message in context: http://old.nabble.com/PROCESSOR_IDENTIFIER%3A-command-not-found-tp28793595p28793595.html
> Sent from the OpenJDK Build Infrastructure mailing list archive at  
> Nabble.com.
>