LISTSERV mailing list manager LISTSERV 16.5

Help for QSERV-L Archives


QSERV-L Archives

QSERV-L Archives


QSERV-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

QSERV-L Home

QSERV-L Home

QSERV-L  November 2014

QSERV-L November 2014

Subject:

Re: Broken linking with new code

From:

"Salnikov, Andrei A." <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Wed, 19 Nov 2014 22:54:54 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (56 lines)

Hi Daniel,

now I see what you mean :)

basically if your LIBS argument contains scons Node object
instead of library name then scons adds path of that Node 
to the command line:

gcc -o build/_cssLib.so ... -lsomelib build/libqserv_css.so

which results in "build/libqserv_css.so" being added to
the shared library NEEDED list instead of libqserv_css.so.
What we need on the command line is

  -Lbuild -lqserv_css

and the only way that I can imagine to make scons do that is 
to add 'qserv_css' string to LIBS instead of Node object. 
You may also need to all 'build' directory to env['LIBPATH'],
not sure if that is needed and how to do it correctly though.

Cheers,
Andy


Daniel L. Wang wrote on 2014-11-19:
> Hi Andrei,
> 
> Please have a look at u/danielw/DM-1395-broken.
> 
> The last commit performs the lib dependency in the most obvious way I
> could think of. It results in "<relpath>/lib<libname>.so" in the linker
> command-line.
> 
> The previous commit tries to decouple the dependency so that the
> "-l<libname>" format is used instead. It isn't done.
> 
> Background: by moving css code to one place, we now have python code in
> two places that depend on it. But these two python packages can be
> loaded at the same time, so directly putting the css symbols in both
> packages' swig libs doesn't work. Hence we create a .so that both swig
> libs can link to. The problem comes because (I think) we don't have
> different stages for building and installing parts of qserv that depend
> on each other. Right now, we build everything, and then install
> everything (so we can't (?) put the dependent .so in its final installed
> place and have the other swig libs point at it during their link stage).
> 
> Thanks for your help,
> -Daniel

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2018
February 2018
January 2018
December 2017
August 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use