[lsst-dm-stack-users] How to update a stack release

[Simon Krughoff]

Dominique,

That log looks truncated.  Can you send the full build log file?  I think
the location of the build file is output when the error is thrown.

Simon


On Mon, Apr 21, 2014 at 12:38 PM, Dominique Boutigny <boutigny at in2p3.fr>wrote:

> Hi,
>
> I finally restarted from scratch with newinstall.sh.
>
> But this time I get the following error while building afw from the master
> branch:
>
>> de -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/pex_config/8.0.0.0
>> +25130f5336/include -I/sps/lsst/dev/lsstprod/DC_
>> 2014/stack_new/Linux64/daf_persistence/master-gde766ea3be+db18872139/include
>> -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/pex_policy/8.0.0.0
>> +0045ad11b7/include -I/sps/lsst/dev/lsstprod/DC_
>> 2014/stack_new/Linux64/pex_logging/8.0.0.0+d78bf4f041/include
>> -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/daf_
>> base/master-g52403476fa+6c6aeb111f/include -I/sps/lsst/dev/lsstprod/DC_
>> 2014/stack_new/Linux64/utils/8.0.0.0+148fa3ac40/include
>> -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/pex_exceptions/8.0.0.0
>> +194681581d/include -I/sps/lsst/dev/lsstprod/DC_
>> 2014/stack_new/Linux64/base/8.0.0.0+ee2f9a34b2/include
>> -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/wcslib/4.14+98989bdd6b/include
>> -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/
>> cfitsio/3310+da39a3ee5e/include -I/sps/lsst/dev/lsstprod/DC_
>> 2014/stack_new/Linux64/gsl/1.15+da39a3ee5e/include
>> -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/
>> minuit2/5.22.00+da39a3ee5e/include -I/sps/lsst/dev/lsstprod/DC_
>> 2014/stack_new/Linux64/xpa/2.1.14+da39a3ee5e/include
>> -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/fftw/3.3.2+da39a3ee5e/include
>> -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/eigen/3.1.1+da39a3ee5e/include
>> -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/
>> mysqlclient/5.1.65+da39a3ee5e/include -I/sps/lsst/dev/lsstprod/DC_
>> 2014/stack_new/Linux64/boost/1.55.0.1+1f726fe9d2/include
>> -I/sps/lsst/dev/lsstprod/DC_2014/stack_new/Linux64/
>> anaconda/1.8.0/include/python2.7 -I/sps/lsst/dev/lsstprod/DC_
>> 2014/stack_new/Linux64/anaconda/1.8.0/lib/python2.7/
>> site-packages/numpy/core/include examples/image2.cc
>> :::::  c++: Internal error: Killed (program cc1plus)
>> :::::  Please submit a full bug report.
>> :::::  See <http://bugzilla.redhat.com/bugzilla> for instructions.
>> :::::  scons: *** [python/lsst/afw/image/imageLib_wrap.os] Error 1
>> :::::  scons: building terminated because of errors.
>>
>
> I am running on Scientific Linux version 6.
>
> Any idea of what could be wrong ?
>
> Dominique
>
> Le 18/04/2014 17:06, Kian-Tat Lim a écrit :
>
>  Dominique,
>>
>>  I tried to follow it but ran into problems, so I tried to restart
>>> from scratch but even if I re-download everything lsst_build keeps
>>> claiming that some packages are already installed.
>>> Is there an option to clear everything completely and rebuild from
>>> scratch ?
>>>
>>         There are three things here: 1) getting the correct version of
>> the source, 2) building from source to installable packages, and 3)
>> installing the packages in your eups stack.  lsst-build is supposed to
>> minimize the amount of cloning for #1 and minimize the building for #2.
>>
>>         If packages are already installed, those should be OK to use.
>> If you have changed the source (either manually or via "lsst-build
>> prepare --ref="), the version number of the package installed in the
>> eups stack should be different.
>>
>>         If you think you have package versions installed that you don't
>> want, you can use "eups remove" to get rid of them, but you have to have
>> removed all packages dependent on them first.  Generally this shouldn't
>> be necessary.
>>
>>         You can clear out the entire build directory used for #1 and #2
>> above by just removing it.  There is no other state.  You can also just
>> start a new build directory.
>>
>>         Clearing out your entire eups stack can also be done by just
>> removing its directory and restarting from newinstall.sh (in a fresh
>> shell).  You can also aim newinstall.sh (again in a fresh shell) at a
>> new stack directory.
>>
>>         Perhaps a log of the errors you are seeing would help?
>>
>>
> --
> Dominique Boutigny  -  CNRS / CC-IN2P3
> Now at SLAC National Accelerator Laboratory
>
> Kavli Building - 221
> Mail     : boutigny at in2p3.fr -  boutigny at slac.stanford.edu
> Office   : +1 650-926-5759   -  Cellular : +1 774-232-0912
>
>
>
> _______________________________________________
> lsst-dm-stack-users mailing list
> lsst-dm-stack-users at lsstcorp.org
> http://listserv.lsstcorp.org/mailman/listinfo/lsst-dm-stack-users
>
>


-- 
K. Simon Krughoff
University of Washington
Department of Astronomy

Physics-Astronomy Bldg.
3910 15th Ave NE
Room C319
Seattle WA 98195-0002
USA

(206)543-9487
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://listserv.lsstcorp.org/pipermail/dm-users/attachments/20140421/6371d0f6/attachment.html>