On Feb 2, 2011, at 1:56 PM, Jonathan Gibbons wrote:

Some messages in the build logs are getting corrupted, perhaps because of parallism. For example,

../../../src/plugin/solaris/jvm_natives/server.c:2031: warning: cast to pointer from integer of different

../../../../src/share/native/sun/security/ec/impl/ec2_163.c:59: warning: ignoring #pragma i

../../../src/plugin/solaris/jvm_natives/native.c:165: warning: type defaults to 'int' in declaration of 'getAw

../../../../src/plugin/solaris/nscore/JavaPluginFactory5.cpp:47: warning: /localtools/linux/gcc29/usr/bin/gcc -O2 -fPIC -DCC_NOEX -W -Wall -Wno-unused -Wno-parentheses -fno-omit-frame-pointer - D_LITTLE_ENDIAN -I../../../../src/plugin/solaris/nscore - I../../../../src/plugin/solaris/nscore/../common -I/HUDSON/workspace/ jdk7-2-build-linux-i586-product/jdk7/build/linux-i586/tmp/ -I/HUDSON/ workspace/jdk7-2-build-linux-i586-product/jdk7/build/linux-i586/tmp/ deploy/headers/plugin -I../../../../src/plugin/solaris/common - I../../../../src/plugin/share/jpiapi -I../../../../src/plugin/ solaris/nscore/../nsstub -I/HUDSON/workspace/jdk7-2-build-linux-i586- product/jdk7/jdk/make/../src/solaris/javavm/export -I/HUDSON/ workspace/jdk7-2-build-linux-i586-product/jdk7/jdk/make/../src/share/ javavm/export -D_GNU_SOURCE -DXP_UNIX -DNO_XEMBED_MOZILLA -DSVR4 - DPLUGIN_NODOTVERSION=\"170\" -DPLUGIN_VERSION=\"1.7.0\" -DVERSION= \"1.7.0-ea-b122\" -DRELEASE=\"1.7.0-ea\" -DARCH=\"i586\" -Di586 - DLIBARCH=\"i386\" -B /localtools/linux/gcc29/usr/bin//../lib/gcc- lib/ -I /localtools/linux/gcc29/usr/bin//../lib/gcc-lib/i386-redhat- linux/egcs-2.9*/include -DRAPTOR_API -DNEW_STREAMING_API -DXP_UNIX - DLINUX -c -o /HUDSON/workspace/jdk7-2-build-linux-i586-product/jdk7/ build/linux-i586/tmp/deploy/plugin/javaplugin_nscp_gcc29/obj/ QueueRunnable.o ../../../../src/plugin/solaris/nscore/ QueueRunnable.cpp

Is this known and/or fixable?

This is due to the 'make -j 4 *.o' that happens when the sharedly library is built. I though GNU make did a better job on keeping the messages grouped with the compile line, but maybe not. It may have to echo out the compile line first. Not sure it can be fixed easily.

Maybe build with ALT_PARALLEL_COMPILE_JOBS=1

-kto


-- Jon

Reply via email to