Hi Jason,

The way to resolve the linking error is incorrect. I submitted a patch
for this. Please check http://review.source.android.com/5285.

Thanks,
Ravi

On Dec 5, 1:22 am, jason <[EMAIL PROTECTED]> wrote:
> Hi rktb,
>
> Thank you for response quickly.
>
> Answer 1:
>
> I am trying to run the binary built on my host x86 computer, because I
> find the following information by typing 'file pvplayer_engine_test' :
>
> pvplayer_engine_test: ELF 32-bit LSB shared object, Intel 80386,
> version 1 (SYSV), not stripped
>
> It is an executable binary on x86, isn't it?
>
> --------------------------------------------------------------------------------------------
> Answer 2 :
>
> The stack trace as follows:
>
> (gdb) bt
> #0  0xb7ce17c6 in __do_global_dtors_aux ()
>
> By the way, I modify the makefile to fix an error as linking
> pvplayer_engine_test. The path of makefile as below:
>
> external/opencore/engines/player/test/build/linux_nj/makefile
>
> I uncomment out the line 53 of this makefile, change it as 'XLDFLAGS
> += -shared'. If you do not change it, there is an error will be
> reported as like:
>
> g++ -o linux/pvplayer_engine_test -L/home/android/external/opencore/
> tools_v2/build/package/nj_rel/installed_lib/linux -L/home/android/
> external/opencore/oscl/SDK/lib/linux -L/usr/lib -L/usr/local/lib linux/
> test_pv_player_engine.o linux/test_pv_player_engine_testset_mio_file.o
> linux/test_pv_player_engine_testset1.o linux/
> test_pv_player_engine_testset5.o linux/
> test_pv_player_engine_testset6.o linux/
> test_pv_player_engine_testset7.o linux/
> test_pv_player_engine_testset8.o linux/
> test_pv_player_engine_testset9.o linux/
> test_pv_player_engine_testset10.o linux/
> test_pv_player_engine_testset11.o linux/
> test_pv_player_engine_testset12.o linux/
> test_pv_player_engine_testset13.o linux/
> test_pv_player_engine_testset_cpmdlapassthru.o -lunit_test_mod_debug -
> lpvcommon_debug -lpvplayer_debug -lpthread -ldl
> /usr/bin/ld: linux/pvplayer_engine_test: hidden symbol
> `__stack_chk_fail_local' in /usr/lib/libc_nonshared.a
> (stack_chk_fail_local.oS) is referenced by DSO
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: ld returned 1 exit status
>
> -------------------------------------------------------------------------------------------
>
> Answer 3 :
>
> I can not see any logs on emulator according to the below topic:
>
> http://groups.google.com/group/android-framework/browse_thread/thread...
>
> I do not know whether or not the pvplayer_engine_test is run
> successfully. Would you like to tell me the more details?
>
> Best Regards
> Jason
>
> On Dec 5, 1:40 pm, rktb <[EMAIL PROTECTED]> wrote:
>
> > Hi Jason,
>
> > Where are you running the x86 executable?
> > Do you have a stack trace of the seg. fault?
> > Yes. We have run the tests on emulator successfully.
>
> > -Ravi
>
> > On Dec 4, 10:10 pm, jason <[EMAIL PROTECTED]> wrote:
>
> > > Hi,
>
> > > The binary built are x86, but the player engine test can not executed.
> > > There is always a segmentation fault is reported. Does anyone run the
> > > test on emulator successfully?
>
> > > Best Regards
> > > Jason
>
> > > On Nov 28, 5:40 am, rktb <[EMAIL PROTECTED]> wrote:
>
> > > > (i) Building the libraries
>
> > > > cd <dir>/external/opencore/tools_v2/build/package/nj_rel
> > > > . ./setup.ksh <dir>/external/opencore
> > > > make -f <dir>/external/opencore/engines/player/build/makefile.conf
>
> > > > (ii) Building the player engine test executable
> > > > cd <dir>/external/opencore/engines/player/test/build/linux_nj
> > > > make
>
> > > > (iii) Building the author engine test executable
> > > > cd <dir>/external/opencore/engines/author/test/build/linux_nj
> > > > make
>
> > > > A couple of notes:
> > > > - Building outside of Android, the method to build is via a recursive
> > > > make system, which is, as expected, very slow. In the next update to
> > > > opencore project, we will provide the facility to build using a non-
> > > > recursive build system to make things much faster.
> > > > - The codebase has not been completely compiled and tested on the
> > > > later versions of gcc, and hence newer warnings crop up. That fails
> > > > the compilation of few libraries that treat warnings as errors. To get
> > > > around this, you may make the following change to get your build
> > > > going:
> > > > In <dir>/external/opencore/tools_v2/build/make/linux_g++_library.mak,
> > > > comment out the line "FLAG_COMPILE_WARNINGS_AS_ERRORS = -Werror".
>
> > > > On Nov 25, 2:50 am, Girish <[EMAIL PROTECTED]> wrote:
>
> > > > > Hi ,
>
> > > > > Is it possible to run the multimedia test cases which are provided in 
> > > > > /
> > > > > external/opencore/engines/player ?
>
> > > > > are u able to test any of them ?
>
> > > > > Regards
> > > > > Girish
>
> > > > > On Nov 15, 10:59 pm, "Android PT" <[EMAIL PROTECTED]> wrote:
>
> > > > > > I think you can build it outside the Android also.
> > > > > > PV has provided an independent test frame work (command line).
> > > > > > So I guess you can build it.
> > > > > > Dependency  : OSCL and underlying kernel.
>
> > > > > > On Sat, Nov 15, 2008 at 10:24 PM, rednoah <[EMAIL PROTECTED]> wrote:
>
> > > > > > > Hi
>
> > > > > > > I extracted /platform/external/opencore dir. from Android source 
> > > > > > > code
> > > > > > > and compile it with attached makefile.
>
> > > > > > > But I got some errors while I did "make".
>
> > > > > > > Does there have a standard rule to build "External Project" 
> > > > > > > outside of
> > > > > > > Android ?
>
> > > > > > > Thanks.
>
> > > > > > > ps. I worked with Fedora 7 , GNU gcc/g++ 4.1.2- Hide quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"android-framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to