Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Thanks!
The problem was with Clucene. With system Clucene the same problem repeated. When I used internal 
Clucen, Its all ok. Still I don,t knoe what is the ploblem with system Clucene.
Thanks again.


Sent from Samsung Mobile

-------- Original message --------
From: Michael Stahl <mstahl@redhat.com> 
Date: 2014/11/26  7:28 PM  (GMT+05:00) 
To: Qurban Ullah <qurbanullah@gmail.com>,libreoffice@lists.freedesktop.org 
Subject: Re: LibreOffice-4.3.4.1 compile error with GCC-4.9.2 
 
On 17.11.2014 15:04, Qurban Ullah wrote:
I tried many time with system libs and without system libs, each time I faced
the same problem.

/build/libreoffice/libreoffice-4.3.4.1/workdir/CxxObject/helpcompiler/source/HelpIndexer_main.o:
In function `main':
HelpIndexer_main.cxx:(.text.startup+0x3b6): undefined reference to
`HelpIndexer::HelpIndexer(rtl::OUString const&, rtl::OUString const&,
rtl::OUString const&, rtl::OUString const&)'
HelpIndexer_main.cxx:(.text.startup+0x3d8): undefined reference to
`HelpIndexer::indexDocuments()'
HelpIndexer_main.cxx:(.text.startup+0x3f1): undefined reference to
`HelpIndexer::getErrorMessage()'

hi Qurban,

i'm unable to reproduce this problem, libreoffice-4-3 branch builds fine
for me with:
gcc (GCC) 4.9.2 20141101 (Red Hat 4.9.2-1)

what does the following print for you:

nm --demangle workdir/CxxObject/helpcompiler/source/HelpIndexer.o |grep
HelpIndexer

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.