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  August 2014

QSERV-L August 2014

Subject:

Re: Problem while building last Qserv master branch

From:

"Daniel L. Wang" <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Tue, 26 Aug 2014 14:55:51 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (44 lines)

Hi Fabrice,

On 08/26/2014 10:06 AM, Fabrice Jammes wrote:
> Build problem of Qserv master branch :
>
> I have next problem while building last Qserv version with g++ (GCC) 
> 4.8.3 20140624 (Red Hat 4.8.3-1)
> Next fix at line 23 of core/modules/xrdfs/SConscript.test solves the 
> problem :
> p = env.Program('testMySqlFs_1.cc', LIBS=["XrdXrootd", *"XrdUtils"*])
> This problem doesn't seems to happen with : g++ (GCC) 4.4.7 20120313 
> (Red Hat 4.4.7-4)
> Do you think we can apply this patch to Qserv master branch ?
I can't reproduce this easily, because I don't have a gcc 4.8 machine 
handy. Does the fix cause any problems for on RHEL6/Centos6 systems?

For now, perhaps it's better to comment it out rather than fix it--the 
xrdfs is likely to go away as soon as the dust settles on the xrootd 
port and the result protocol.

> Qserv dependencies versions management in eups :
>
> Furthermore, i see that Qserv master branch doesn't use a new xrootd 
> version.
> For now I don't know the right procedure to force a given Qserv 
> version to use a given version of its dependencies.
> It seems it is possible to do this with the rebuild command of lsstsw, 
> but how ?
> Please note that this problem seems to be the same than the one 
> described in qserv-l mail named : "Redundant(?) installation of doxygen"
I don't know how to solve this. I don't think it's a problem for new 
installations, because I think buildbot builds everything from scratch 
and it seems to build and test qserv without error. Perhaps your local 
eups stack doesn't know about the new xrootd package? Maybe there is 
something you can do with your installation to refresh package versions.

-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