Page 3 of 4
Re: Next step after telnet access?
Posted: Thu Aug 15, 2013 12:46 pm
by patois
I'm stuck at compiling memjack
Code: Select all
dennis@ubuntu:~/Downloads/memjack$ make
arm-v7a8v2r2-linux-gnueabi-gcc memjack.o util.o procutils.o -o memjack
arm-v7a8v2r2-linux-gnueabi-gcc: selected multilib '.' not installed
make: *** [memjack] Error 1
any ideas?
Re: Next step after telnet access?
Posted: Thu Aug 15, 2013 1:11 pm
by juusso
what compiller have u used? from svn or from opensource?
Re: Next step after telnet access?
Posted: Thu Aug 15, 2013 1:13 pm
by patois
the one from svn that you pointed me to.
edit: the samsung toolchain did it, thanks
Re: Next step after telnet access?
Posted: Thu Aug 15, 2013 5:18 pm
by juusso
isn't the problem solimilar to described here?
http://stackoverflow.com/questions/3900 ... th-64bit-g
I mean you miss either gcc-multilib or g++-multilib or both...?
Re: Next step after telnet access?
Posted: Thu Aug 15, 2013 5:40 pm
by patois
Thanks, it works using the samsung toolchain
Re: Next step after telnet access?
Posted: Thu Aug 15, 2013 5:56 pm
by juusso
hmm, problem, need to understand what's wrong with svn.
Re: Next step after telnet access?
Posted: Thu Aug 15, 2013 8:17 pm
by bugficks
maybe its as simple as using --disable-multilib when compiling toolchain?
Re: Next step after telnet access?
Posted: Sat Aug 17, 2013 8:31 am
by juusso
patois wrote:the one from svn that you pointed me to.
edit: the samsung toolchain did it, thanks
Re-uploaded E series toolchain to svn.
Committed revision 1348.
Now memjack compiled w/o errors
memjack# make
arm-v7a8v2r2-linux-gnueabi-gcc -std=gnu99 -O2 -c -o memjack.o memjack.c
arm-v7a8v2r2-linux-gnueabi-gcc -std=gnu99 -O2 -c -o util.o util.c
arm-v7a8v2r2-linux-gnueabi-gcc -std=gnu99 -O2 -c -o procutils.o procutils.c
arm-v7a8v2r2-linux-gnueabi-gcc memjack.o util.o procutils.o -o memjack
Update:
oops. After checkout - same error??? Seems some of files/permissions aren`t passed to svn... grr...[/off]
Re: Next step after telnet access?
Posted: Sat Aug 17, 2013 8:54 am
by patois
good
memjack worked fine for me after I had adjusted the patch structure to my exeDSP version, so it does not cause my TV to reboot due to having detected a debugger. Still, I haven't been able to properly debug exeDSP using IDA and gdbremote. Also haven't yet figured out why it doesn't work and whether it is related to IDA or the gdbserver build I took from SamyGo. Did anyone ever successfully debug exeDSP using gdbremote (on an E model)? breakpoints don't seem to be handled properly and somehow single stepping code doesn't work either.
Re: Next step after telnet access?
Posted: Sat Aug 17, 2013 8:59 am
by juusso
AFAIK Denny worked with debugger and got success. I ping him.