harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gregory Shimansky <gshiman...@gmail.com>
Subject Re: [drlvm][smoke_test] running kernel classes tests on DRLVM compiled with Intel Compiler (linux/ia32)
Date Tue, 24 Oct 2006 14:06:16 GMT
BTW to test how things work with Intel compiler I've installed it on Gentoo 
(version 9.1.042, it is marked as unstable, but the most recent "stable" is 
very old - 7.1.006... which version do you use?) and failed to compile drlvm 
with it. Something is wrong with thread manager linking

       [cc] 0 total files to be compiled.
       [cc] Starting link
       [cc] ld: tm_self_tls: TLS definition in ../_obj/thread_native_basic.o 
section .tbss mismatches non-TLS reference in ../_obj/thread_native_condvar.o
       [cc] ../_obj/thread_native_condvar.o: could not read symbols: Bad value


Does anyone know what's wrong and how to fix it? I tried to understand how 
tm_self_tls is defined and couldn't, because its definition and usage in 
different files is quite complicated. Maybe I need newer binutils (current 
version is 2.16.1-r3 - latest stable), the "Bad value" seems to hint on this.

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?
> Thanks.
> --
> Nataly Naumova,
> Intel Middleware Products Division

Gregory Shimansky, Intel Middleware Products Division

View raw message