harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <g...@pobox.com>
Subject Re: [drlvm][smoke_test] running kernel classes tests on DRLVM compiled with Intel Compiler (linux/ia32)
Date Wed, 25 Oct 2006 05:46:04 GMT

Gregory Shimansky wrote:
> Hello Nataly
> It looks like a workaround to me to run the tests for VM. To run other user 
> applications we need a general solution about what to do with non standard 
> libraries which Intel compiler links with.
> On Gentoo if you install icc, the system adds an entry to 
> autogenerated /etc/ld.so.conf with path to Intel compiler installation to 
> automatically include these libraries to linking path, but it seems not to be 
> the case for other distributions like yours.

How useful is this if you want to give the binary to someone else?


> On Tuesday 24 October 2006 13:07 Nataly Naumova wrote:
>> Hi everybody.
>> I've found out that the kernel classes smoke tests (for DRLVM built by
>> Intel Compiler on Linux/ia32) are failed because of wrong enironment
>> set in "-run-kernel-test" target. The output message is
>> "..build/lnx_ia32_icc_debug/deploy/jre/bin/java: error while loading
>> shared libraries: libimf.so: cannot open shared object file: No such
>> file or directory".
>> The reason is that LD_LIBRARY_PATH is not set for this target in build
>> scripts, but libimf.so is needed for the classes loading.
>> As I understand LD_LIBRARY_PATH is not needed for classes loading for
>> DRLVM compiled by gcc, so everything is ok for gcc builds. This
>> variable was set for this target earlier, the string with
>> LD_LIBRARY_PATH setting is commented in make/targets/kernel.test.xml.
>> Does anybody knows why it was commented?
>> I've sent the patch which just comments the strings out
>> (HARMONY-1946)
>> -                    <!--env key="LD_LIBRARY_PATH"
>> value="${build.deploy.dir}/bin:${env.LD_LIBRARY_PATH}" /-->
>> +                    <env key="LD_LIBRARY_PATH"
>> value="${build.deploy.dir}/bin:${env.LD_LIBRARY_PATH}" />
>> Could anybody commit this?

View raw message