Ok, also Bill -

If you get things installed, then you can get test data, already
in myisam tables, and a emptyChunks.txt, and a shell script
to load the qms.  This should give you a setup ready to go for
testing.  I put the data and shell scripts on lsst-db2, at:

/u2/qserv/pt11_mysql

So, take a look there, and see if you can use that.

Douglas


On 09/30/2013 01:02 PM, Bill Chickering wrote:
> Hi Douglas, Hi Fabrice -
>
> Success! (I think) Looks as though I successfully built and installed qserv (ticket 3007) on lsst-dev03 using the latest scons script. Note that there remains the issue of launchpad.net (scisql archive) being unreachable from our intranet, however. I am able to work around this by manually copying the scisql archive to my home directory and including the following lines within qserv-build.conf:
> [dependencies]
> scisql_url=file:///u/ki/bchick/qserv_build/scisql-0.3.2.tar.bz2
>
> But everything else looks good!
>
> Next, I plan to manually copy over LSST data, along with metadata, from the mysql instance associated with my preexisting qserv instance. I'll let you know how this goes.
>
> Thanks,
> Bill
>
>
> On Sep 30, 2013, at 9:44 AM, Douglas Smith <[log in to unmask]> wrote:
>
>> Ok, hey Bill -
>>
>> Turns out I have sudo priviledge on lsst-dev03.  The standard install
>> procedure now is that you first run :
>>
>> admin/bootstrap/qserv-install-deps-sl6.sh
>>
>> On the machine as root to get the needed rpm packages installed
>> there, and up to date.  So, I did that on the machine.
>>
>> So, you can try again, like Fabrice says, with the scons uninstall, and
>> scons again and see how it goes now.
>>
>> Douglas
>>
>>
>>
>> On 09/30/2013 01:19 AM, Fabrice Jammes wrote:
>>> Hello Bill,
>>>
>>> Sorry Bill but I can't reproduce your problem with scons of my machine.
>>> Nevertheless, I suspect a conflict in scons versions.
>>>
>>> Furthermore, it seems you have qserv code here :
>>> /u1/bchick/sandbox2/qserv-branchtest/
>>> and install dir here :
>>> /u1/bchick/sandbox2/
>>>
>>> First, i strongly recommand you to extract qserv source code from qserv install dir,
>>> for example move it in :
>>> /u1/bchick/src/qserv-branchtest/
>>>
>>> Then in /u1/bchick/src/qserv-branchtest/ run :
>>> scons uninstall
>>> and then :
>>> scons
>>>
>>> If your still meeting the scons issue you report, here's a few questions which should help you in diagnose it :
>>>
>>> *1. *Do you have "scons" rpm provided by SL6 installed on your system ?
>>> (do you have launched, under root account, the script %QSERV_SRC_DIR/admin/bootstrap/qserv-install-deps-sl6.sh which install it ?)
>>>
>>> *2.* Do you use this rpm version :
>>> Here's what i get after having installed qserv distribution dependencies with qserv-install-deps-sl6.sh :
>>>
>>> [fjammes@clrlsst-dbmaster-vm qserv]$ which scons
>>> */usr/bin/scons*
>>>
>>> If you don't get the same path, it is possible that you still run a compiled version of scons, which was installed by previous versions of Qserv.
>>> In this case run
>>> scons uninstall
>>> and then check that
>>> which scons
>>> give the same output than me.
>>> *
>>> **3. *If the above is ok and the problem still persist, which version of scons do you have ?
>>> Here's mine :
>>> [fjammes@clrlsst-dbmaster-vm qserv]$ scons --version
>>> SCons by Steven Knight et al.:
>>>     script: v2.0.1.r5134, 2010/08/16 23:02:40, by bdeegan on cooldog
>>>     engine: v2.0.1.r5134, 2010/08/16 23:02:40, by bdeegan on cooldog
>>> Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 The SCons Foundation
>>>
>>> *4. *If the problem still persist, please could you try launching the attached script ?
>>> It will install qserv (same as qserv-install, but in shell and for qserv-master only)
>>> and give me the failure message.
>>>
>>> Thanks,
>>>
>>> Fabrice
>>>
>>>
>>> On 09/27/2013 11:21 PM, Kian-Tat Lim wrote:
>>>> Serge,
>>>>
>>>>> I think scons might be ignoring the ambient environment (PATH,
>>>>> LD_LIBRARY_PATH, etc...) when it is run, instead setting up its own
>>>>> (presumably in the name of providing repeatable builds).
>>>> 	scons does not by default pass variables from the environment in
>>>> which it is invoked to the processes it invokes, precisely to provide
>>>> repeatable builds.
>>>>
>>>> | scons does not automatically propagate the external environment used to
>>>> | execute scons to the commands used to build target files. This is so
>>>> | that builds will be guaranteed repeatable regardless of the environment
>>>> | variables set at the time scons is invoked. This also means that if the
>>>> | compiler or other commands that you want to use to build your target
>>>> | files are not in standard system locations, scons will not find them
>>>> | unless you explicitly set the PATH to include those locations. Whenever
>>>> | you create an scons construction environment, you can propagate the
>>>> | value of PATH from your external environment as follows:
>>>> |
>>>> |     import os
>>>> |     env = Environment(ENV = {'PATH' : os.environ['PATH']})
>>>>

########################################################################
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