log4cplus-devel

Re: [Log4cplus-devel] A problem while make file

[Václav Z. <wi...@us...>]

On Fri, 4 Nov 2011 03:21:49 +0000, Boom LBoom wrote:
> Dear Sir/Madam,
>
> Please suggest solution to solve my problem when I make log4cplus.
>
> I got error message while "make" command. The error shows as below.
>
> ld: warning: relocation error: R_386_32: file 
> .libs/consoleappender.o:
> symbol std::cout: external symbolic relocation against 
> non-allocatable
> section .debug_info; cannot be processed at runtime: relocation
> ignored
> ld: warning: relocation error: R_386_32: file 
> .libs/consoleappender.o:
> symbol std::cerr: external symbolic relocation against 
> non-allocatable
> section .debug_info; cannot be processed at runtime: relocation
> ignored
> ld: warning: relocation error: R_386_32: file 
> .libs/consoleappender.o:
> symbol std::cout: external symbolic relocation against 
> non-allocatable
> section .debug_info; cannot be processed at runtime: relocation
> ignored
> ld: warning: relocation error: R_386_32: file 
> .libs/consoleappender.o:
> symbol std::cerr: external symbolic relocation against 
> non-allocatable
> section .debug_info; cannot be processed at runtime: relocation
> ignored
> ld: warning: relocation error: R_386_32: file .libs/loglog.o: symbol
> std::cout: external symbolic relocation against non-allocatable
> section .debug_info; cannot be processed at runtime: relocation
> ignored
> ld: warning: relocation error: R_386_32: file .libs/loglog.o: symbol
> std::cerr: external symbolic relocation against non-allocatable
> section .debug_info; cannot be processed at runtime: relocation
> ignored
> ld: warning: relocation error: R_386_32: file .libs/loglog.o: symbol
> std::cout: external symbolic relocation against non-allocatable
> section .debug_info; cannot be processed at runtime: relocation
> ignored
> ld: warning: relocation error: R_386_32: file .libs/loglog.o: symbol
> std::cerr: external symbolic relocation against non-allocatable
> section .debug_info; cannot be processed at runtime: relocation
> ignored
>
> Environment as my project
> Server = HP Prolant G5 (CPU Intel)
> OS = Solaris 10 (i386)
> Compiler = GCC version 4.4.2
I have never seen this problem before. It is only a warning, does the 
resulting liblog4cplus work for you? Is the 'ld' your GCC is using the 
GNU ld? What version of log4cplus are you compiling?

(...after some searching...)

Please try to add -gstabs+ to the CXXFLAGS, e.g., ./configure 
CXXFLAGS=-gstabs+ etc.

-- 
VZ

Re: [Log4cplus-devel] A problem while make file

[Václav Z. <wi...@us...>]

On Mon, 7 Nov 2011 03:43:13 +0000, Boom LBoom wrote:
> Hi VZ,
>
> Thank you for your replying.
>
> From your questions
>  I have never seen this problem before. It is only a warning, does 
> the
> resulting liblog4cplus work for you?
> answer : It was compiled success but that occurred error while ld
>
> Is the 'ld' your GCC is using the GNU ld?
> answer : ld: Software Generation Utilities - Solaris Link Editors:
> 5.10-1.1505
>
> What version of log4cplus are you compiling?
> answer : log4cplus version 1.0.3
>
> After trying from your recommended. The result shows as below so it
> didn't work.
>
> -bash-3.2$ cat config.log
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
>
> It was created by log4cplus configure 1.0.3, which was
> generated by GNU Autoconf 2.62. Invocation command line was
>
>  $ ./configure CXXFLAGS=-gstabs+
>[...]
> configure:2764: checking for C++ compiler default output file name
> configure:2786: g++ -gstabs+ conftest.cpp >&5
> Assembler: conftest.cpp
>  "/var/tmp//ccH4txrq.s", line 39 : Illegal mnemonic
>  Near line: " .stabd 46,0,0"
>  "/var/tmp//ccH4txrq.s", line 39 : Syntax error
>  Near line: " .stabd 46,0,0"
>  "/var/tmp//ccH4txrq.s", line 59 : Illegal mnemonic
>  Near line: " .stabd 78,0,0"
>  "/var/tmp//ccH4txrq.s", line 59 : Syntax error
>  Near line: " .stabd 78,0,0"
>[...]
I see three possibilities: I you can either live with the warning, or 
disable debugging information generation altogether, or get GCC that 
uses GNU ld. I do not think that this is log4cplus specific problem but 
rather a compiler tool chain problem on Solaris.


-- 
VZ