On 22.08.2013 18:16, 張仁瀚 wrote:
> Thanks a lot! It seems that I have fixed this error by replacing those
> source code provided by your link [2]. It had continued building for a long
> time but I bumped into another error...
>
> **
> ERROR: ERROR: un
Thanks a lot! It seems that I have fixed this error by replacing those
source code provided by your link [2]. It had continued building for a long
time but I bumped into another error...
**
ERROR: ERROR: unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JR
Hi Yohey,
On 21.08.2013 20:22, 張仁瀚 wrote:
> Well,thank you for your help. I learned a lot but I got a new error that I
> can't fix it. It looks like something happened to the module svgio.
>
> Here is the log:
>
> $ build debug=true --all
> ...
> ...
> ...
> /home/yohey/AOO/aoo-trunk/main/svgio/
Well,thank you for your help. I learned a lot but I got a new error that I
can't fix it. It looks like something happened to the module svgio.
Here is the log:
$ build debug=true --all
...
...
...
/home/yohey/AOO/aoo-trunk/main/svgio/source/svgreader/svgsvgnode.cxx:636:71:
error: taking address o
On 21.08.2013 11:07, 張仁瀚 wrote:
> Thanks for your help.
> But I can't build with debug=1, even I had do that with a new clean sources.
> I can use "build killobj ; build debug=1" in the source which has been
> built once previously. But it still didn't work and get a message "no
> debugging symbols
Hello,
Thanks for your help.
But I can't build with debug=1, even I had do that with a new clean sources.
I can use "build killobj ; build debug=1" in the source which has been
built once previously. But it still didn't work and get a message "no
debugging symbols found" when I ran AOO with gdb ju
Apache OpenOffice uses both dmake and gnu-make build systems. We know
that is a PITA and the project will clean this historical mess up in the
future.
Enabling debug symbols is done by using a "debug=1" parameter in the
module of interest. For dmake modules you do
build killobj ; build debug=1
when you build something with gcc with -g option, gdb will find debugging
symbols. So maybe soffice.bin has been optimized to some extent.
2013/8/19 ��仁瀚
> Hello everyone,
>
> Recent days I have tried to run AOO with GDB dor debugging. But
> after I ran it(enter gdb ./soffice.bin), I got a mess
Hello everyone,
Recent days I have tried to run AOO with GDB dor debugging. But
after I ran it(enter gdb ./soffice.bin), I got a message said no
debugging symbols found. And then I typed "list", I got "No symbol
table is loaded".
Here is log:
$ gdb ./soffice.bin
GNU gdb (Ubuntu/Linaro 7.4-2012.0
