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


Ok, now build goes on.
Tried to figure out this, looks like libstdc++ is not correctly linked:
Undefined                       first referenced
symbol                             in file
std::basic_string
, std::allocator
::basic_string(std::basic_string
, std::allocator
&) 
/sources/sonicle/xstream-desktop-gate/components/libreoffice/libreoffice/libreoffice-4.4.0.2/workdir/CxxObject/l10ntools/source/idxdict/idxdict.o
ld: fatal: symbolreferencing errors. No output written to 
/sources/sonicle/xstream-desktop-gate/components/libreoffice/libreoffice/libreoffice-4.4.0.2/workdir/LinkTarget/Executable/idxdict
collect2: error: ld returned 1 exit status
----------------------------------------------------------------------------------
Da: Richard PALO
A: gbulfon@sonicle.com Norbert Thiebaud
Cc: Michael Stahl
libreoffice
Data: 18 gennaio 2015 22.56.51 CET
Oggetto: Re: 4.4.0.1 build error on sal/types.h on solaris/illumos
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 18/01/15 21:33, Gabriele Bulfon a écrit :
Ok, I commented out these on Solaris.mk:
#ifneq ($(gb_DEBUGLEVEL),0)
#gb_LINKEROPTFLAGS :=
#else
#gb_LINKEROPTFLAGS := -Wl,-O1
#endif
will let you know :)
----------------------------------------------------------------------------------
Da: Norbert Thiebaud
A: gbulfon@sonicle.com
Cc: Michael Stahl
libreoffice
Richard PALO
Data: 18 gennaio 2015 20.15.22 CET
Oggetto: Re: 4.4.0.1 build error on sal/types.h on solaris/illumos
On Sun, Jan 18, 2015 at 12:18 PM, Gabriele Bulfon
wrote:
Ok, I checked and it looks fine, so solaris.mk should be taken.
Also config.log shows correct variables for OS, CPU and COM.
What actually happens is during make, after it has downloaded and extracted
various stuff.
The last one is translations file.
Then it goes on building concat-deps, and linking fails:
[build C ] solenv/bin/concat-deps.c
[build LNK] Executable/concat-deps
ld: fatal: unrecognized option '-O'
ld: fatal: unrecognized option '-1'
ld: fatal: use the -z help option for usage information
collect2: error: ld returned 1 exit status
Maybe just concat-deps have problems linking with wrong options on Solaris?
Yes it is quite possible... concat-deps is a small utility I wrote to
speed up the original perl-based one... and I'm quite sure I never
tried to link it on Solaris.
Otoh concat-deps is built using the standard gbuild mechanism for that:
see solenv/Executable_concat-deps.mk
so it is more likely that the problem is generic and that concat-deps
just happen to be the first one to be linked.
BTW, is there any way to issue gmake and let it show what command "LNK" is
doing?
It tried forcing a "-n" but I did not get the command debugged....
verbose=t make
Norbert
Yeah, this should go as not valid for solaris ld.
Apparently comes from here:
commit 3c4cd1deaf71d0d800957b3580d426c721bf7844
Author: Jonathan Adams
Date:   Fri Mar 16 21:50:37 2012 +0100
gbuild: switch solaris.mk to GCC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJUvCwiAAoJECAB22fHtp27MBMH/2IYZRT44q8six0NjeXYkG6B
vDe0AJund3FTcN/t9zT0bpFx9mPCCdVxWbqqdv0CFKYQrfSLhPRaksuWrAnK1mOI
Nl5vcDxI8D0ls6N1c40ZIAcpI3mOeY1Xye6rpKwYJSjWxqOZHxgWEMMvIrzd9Jxb
wnChiTHrDj4ljX1QCPWLxJQB0+e3gXrFmcLvQSEhIPslGPou4i14ur3tf2vVwk0a
FZzCoiYfCnUil7vQJHA8vUtbVASMxX4sJ6iYOfD0K/Z+11c4PwF4xZZtZCtG6Rek
qLd/Yz/OhqIg2POqJeaDL8S9fYOfrWUgfKuwcFhqBgqDQMknQH8DSeJt6IPAea0=
=ZdNh
-----END PGP SIGNATURE-----

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.