Right... but am I supposed to unpack the scisql tar-ball by hand?
I am still missing something. Let's move to hipchat qserv room maybe?





On 09/30/2014 12:10 PM, Serge Monkewitz wrote:
> Jacek,
>
>      scisql has always depended on waf, but the scisql source tree
> includes it (it’s a single self-extracting file). There should be no
> need to install your own copy, and in fact doing so may be dangerous (if
> you pick a version that is incompatible with scisql’s wscript).
> Furthermore, since you ran waf yourself, you are omitting a bunch of
> configuration paramers (e.g. where is mysql, where is the eups install
> directory, etc…). If you insist on not building via eups, then look here
> for the configure options that eups uses:
> https://git.lsstcorp.org/cgit/LSST/external/scisql.git/tree/ups/eupspkg.cfg.sh
>
> Note that Fabrice has included a new scisql tar-ball in the LSST
> repository, so I don’t think K-T’s analysis is correct.
>
>
> On Sep 30, 2014, at 11:57 AM, Jacek Becla <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
>
>> All right, but it looks like we now are depending on waf...
>>
>> eupspkg -er build
>> The project was not configured: run "waf configure" first!
>>
>>
>> ok, so I installed waf, and
>>
>> [becla@lsst-dbdev5 scisql]$ waf configure
>> Setting top to                           :
>> /usr/local/home/becla/qservDev/repos/scisql
>> Setting out to                           :
>> /usr/local/home/becla/qservDev/repos/scisql/build
>> Checking for 'gcc' (c compiler)          : /usr/bin/gcc
>> Checking for mysql install               : Undefined mysql header
>> directory, use --help option.
>> (complete log in
>> /usr/local/home/becla/qservDev/repos/scisql/build/config.log)
>>
>>
>> This is getting way too convoluted than it should be!
>>
>> How do I put on our distrib server what Fabrice has?
>>
>> I am lost
>>
>> Jacek
>>
>>
>>
>>
>>
>> On 09/30/2014 11:45 AM, Kian-Tat Lim wrote:
>>>> but if I try to patch an existing stack by git cloning scisql
>>>> 0.3.3, it does not appear anywhere
>>>>
>>>> setup -r .
>>>
>>> You need "eupspkg -er prep" here, I think.
>>>
>>>> eupspkg -er build
>>>> eupspkg.build: no build system detected; assuming no build needed.
>>>
>>> It's not finding configure because it didn't expand the tarball.
>>>
>>
>> ########################################################################
>> 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
>

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