Project Home
Project Home
Source Code
Source Code
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - multiple definitons of linking errors: (5 Items)
   
multiple definitons of linking errors  
Hi,

We are creating an executable file using make file for the application, the object file is creating sccessfully, but 
when linking its giving multiple definitons of errors.

The compiler options are: ntox86-g++-3.3.5 -c -g
-fmessage_length=72 -Wno_sign_compare, and

the linking options are: ntox86-g++-3.3.5 -lboost_filesystem-d 
-lboost_date_time-d -lboost_thread-mt-d -lMCLog 

Here I am attaching the errors text.

any help would be appriciated.

Regards,
Lakshmi.
Attachment: Text error.txt 1.75 KB
Re: multiple definitons of linking errors  
Lakshmi Narasaiah wrote:
> Hi,
> 
> We are creating an executable file using make file for the application, 
> the object file is creating sccessfully, but when linking its giving 
> multiple definitons of errors.
> 
> The compiler options are: ntox86-g++-3.3.5 -c -g
> -fmessage_length=72 -Wno_sign_compare, and
> 
> the linking options are: ntox86-g++-3.3.5 -lboost_filesystem-d
> -lboost_date_time-d -lboost_thread-mt-d -lMCLog
> 
> Here I am attaching the errors text.
> 
> any help would be appriciated.

Hi Lakshmi,

How did you create libMCLog? Did you create libMCLog.so with -shared? 
Some of the duplicate symbols are from our startup crt files that only 
get linked into executables and so there shouldn't be copies of them in 
your shared object.

Regards,

Ryan Mansfield
Re: multiple definitons of linking errors  
> Lakshmi Narasaiah wrote:
> > Hi,
> > 
> > We are creating an executable file using make file for the application, 
> > the object file is creating sccessfully, but when linking its giving 
> > multiple definitons of errors.
> > 
> > The compiler options are: ntox86-g++-3.3.5 -c -g
> > -fmessage_length=72 -Wno_sign_compare, and
> > 
> > the linking options are: ntox86-g++-3.3.5 -lboost_filesystem-d
> > -lboost_date_time-d -lboost_thread-mt-d -lMCLog
> > 
> > Here I am attaching the errors text.
> > 
> > any help would be appriciated.
> 
> Hi Lakshmi,
> 
> How did you create libMCLog? Did you create libMCLog.so with -shared? 
> Some of the duplicate symbols are from our startup crt files that only 
> get linked into executables and so there shouldn't be copies of them in 
> your shared object.
> 
> Regards,
> 
> Ryan Mansfield


Hi Ryan,

Initially I created libMCLog.so with -Bdynamic, so that got the linking errors. 
Later it is created with -shared, now the executable is creating properly.

Thanks for the inputs Ryan..

I have another query regarding warings that, 

when I do make the warnings are as follows:

 instantiated from `Log<Log_info, Formatter_type, Destination>::Log() [with Log_info = Exception_info, Formatter_type = 
XML_exception_formatter, Destination = Output_to_xmlfile<XML_exception_formatter>]'

attaching the warnings log list.

any help would appriciate.

Regards,
Lakshmi.


Attachment: Text warnings.txt 617 bytes
Re: multiple definitons of linking errors  
> when I do make the warnings are as follows:
> 
>  instantiated from `Log<Log_info, Formatter_type, Destination>::Log() [with Log_info = Exception_info, Formatter_type
>  = XML_exception_formatter, Destination = Output_to_xmlfile<XML_exception_formatter>]'
> 
> attaching the warnings log list.
> 

It looks like the same problem as before as the multiline warnings/errors being parsed incorrectly. Can you use -
fmessage-length=0 instead of -fmessage-length=72?

Regards,

Ryan Mansfield

Re: multiple definitons of linking errors  
> > when I do make the warnings are as follows:
> > 
> >  instantiated from `Log<Log_info, Formatter_type, Destination>::Log() [with Log_info = Exception_info, 
> Formatter_type
> >  = XML_exception_formatter, Destination = Output_to_xmlfile<XML_exception_formatter>]'
> > 
> > attaching the warnings log list.
> > 
> 
> It looks like the same problem as before as the multiline warnings/errors 
> being parsed incorrectly. Can you use -fmessage-length=0 instead of -fmessage-
> length=72?
> 
> Regards,
> 
> Ryan Mansfield
> 


Hi Ryan,

Now the problem is resolved.

Thanks a lot.

Regards,
Lakshmi.