[Bug 53895] Linker doesn't handle the references in .a libraries located in different directories properly

[Claudiu ANGHEL]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=53895     




------- Additional Comments From claudiu.anghel at skynet.be  2003-02-09 17:41 -------
Subject: Re:  Linker doesn't handle the references in .a libraries
 located in different directories properly

Thank you for your response,

Unfortunately the LDADD line is generated by KDevelop and any 
modification will be overwriten every time you change the directory 
structure.
Is very strange that if you don't link the .a archives but .o objects 
you have no linking problem.
For the moment I'm making a dummy call in a dummy function in the main 
directory for forcing the linking of the contents of library.
Maybe I should download kdevelop 3.0, but I'm not so confident in alpha 
versions.

Thank you once more,
Claudiu ANGHEL

Caleb Tennis wrote:

>------- You are receiving this mail because: -------
>You reported the bug, or are watching the reporter.
>     
>http://bugs.kde.org/show_bug.cgi?id=53895     
>caleb at aei-tech.com changed:
>
>           What    |Removed                     |Added
>----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |RESOLVED
>         Resolution|                            |INVALID
>
>
>
>------- Additional Comments From caleb at aei-tech.com  2003-02-09 17:27 -------
>This would work better if you switch the order: 
> 
>bugtest_LDADD = ./dirb/libdirb.a ./dira/libdira.a 
> 
>GCC compiling is very specific about the order of static libraries when they 
>have dependencies on each other.  I don't remember if you can switch the order 
>easily in KDevelop 2.x, but you can in 3.0.
>
>
>  
>