Antonio,<br> Thanks. I checked out and did dpkg buildpackage -us -uc -nc -d. It failed with the following error. Looks like xpidl under microb-engine is missing. Do I need to build and install xpidl separately? I already installed libidl-dev.
<br><br>-------<br>/scratchbox/tools/bin/sh: line 1: /usr/lib/microb-engine/xpidl: No such file or directory<br>make[3]: *** [gtkmozembedmarshal.h] Error 127<br>make[3]: Leaving directory `/home/skumar/libgtkembedmoz/obj-arm-linux-gnueabi/sr c'
<br>make[2]: *** [all-recursive] Error 1<br>make[2]: Leaving directory `/home/skumar/libgtkembedmoz/obj-arm-linux-gnueabi'<br>make[1]: *** [all] Error 2<br>make[1]: Leaving directory `/home/skumar/libgtkembedmoz/obj-arm-linux-gnueabi'
<br>make: *** [build-stamp] Error 2<br>-------<br><br>On side notes, I mistakenly did apt-get install libgtkmozembed (not libgtkembedmoz) and after that It seemed to do something better, but failed eventually. I got the following error while Xphyr/af-fb.. is active.
<br><br>-------<br>[sbox-SDK_ARMEL: ~/microb-engine-1.0.3/build-tree/obj-edyn-arm-sb-buildgtk2/dist/bin] > export GRE_HOME=.<br>[sbox-SDK_ARMEL: ~/microb-engine-1.0.3/build-tree/obj-edyn-arm-sb-buildgtk2/dist/bin] > export USE_LOCAL_GRE=1
<br>[sbox-SDK_ARMEL: ~/microb-engine-1.0.3/build-tree/obj-edyn-arm-sb-buildgtk2/dist/bin] > export DISPLAY=:2<br>[sbox-SDK_ARMEL: ~/microb-engine-1.0.3/build-tree/obj-edyn-arm-sb-buildgtk2/dist/bin] > ./run-mozilla.sh
./TestGtkEmbed <a href="http://www.google.com">www.google.com</a><br>defined GRE_HOME=.<br>defined DISPLAY=:2<br>new_gtk_browser<br> menu bar<br> tool bar<br> location bar<br> status bar<br>qemu: uncaught target signal 11 (Segmentation fault) - exiting
<br>--------<br><br>I then closed Xephyr, and then I got the following error.<br><br>--------------<br>[sbox-SDK_ARMEL: ~/microb-engine-1.0.3/build-tree/obj-edyn-arm-sb-buildgtk2/dist/bin] > ./run-mozilla.sh ./TestGtkEmbed
<a href="http://www.google.com">www.google.com</a><br>defined GRE_HOME=.<br>defined DISPLAY=:2<br>Unsupported setsockopt level=1 optname=9<br>Unsupported setsockopt level=1 optname=9<br>Unsupported setsockopt level=1 optname=9
<br>Unsupported setsockopt level=1 optname=9<br>Unsupported setsockopt level=1 optname=9<br>Unsupported setsockopt level=1 optname=9<br>TestGtkEmbed[4031]: GLIB WARNING ** Gtk - cannot open display:<br>-------------<br><br>
Thanks, <br>SP<br><br><br><div><span class="gmail_quote">On 8/29/07, <b class="gmail_sendername">Antonio Gomes</b> <<a href="mailto:tonikitoo@gmail.com">tonikitoo@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
sp,<br><br>have you installed libgtkembedmoz as well ?<br><a href="https://garage.maemo.org/svn/browser/mozilla/trunk/libgtkembedmoz/">https://garage.maemo.org/svn/browser/mozilla/trunk/libgtkembedmoz/</a><br><br>maybe installing it, and trying something like:
<br><br>$ cd /usr/lib/microb-engine<br>$ export GRE_HOME=.<br>$ export LD_LIBRARY_PATH=.<br>$ ./run-mozilla.sh ./TestGtkEmbed <a href="http://google.com">google.com</a><br><br>?<br><br>On 8/29/07, S P <<a href="mailto:pskrtech@gmail.com">
pskrtech@gmail.com</a>> wrote:<br>> With the help of timelyx and pupnik (IRC), I was able to build microb. I<br>> have microb-engine_1.0.3-13_armel.deb and other .debs under<br>> SDK_ARMEL. I tried dpkg -i and installation was successful (I had to install
<br>> other .debs to get there).<br>><br>> But I am not able to see Microb under Web in maemo (Xephyr).<br>><br>> In some IRC log, I found that I need to do<br>><br>> GRE_HOME=. and USE_LOCAL_GRE=1<br>
> and ./run-mozilla.sh ./TestGtkEmbed<br>><br>> If I do this, yesterday I got error related to starting xpcom.<br>><br>> Today, I am getting -- Couldn't find GTKMozEmbed symbols.<br>><br>> Can somebody help me how to run the microb I built?
<br>><br>> As you can see, I built for SDK_ARMEL. Do I need to built for X86?<br>> In some IRC log I found that microb does not build for X86.<br>><br>><br>> How can I see my armel .deb running? Do I need to use QEMU ( I need to read
<br>> about it yet)<br><br>btw, try building it for i386 first ...;)<br><br><br><br>--<br>--Antonio Gomes<br></blockquote></div><br>