<div dir="ltr">Thanks for the bug report! Knowing that this is triggered by overly-aggressive will really help us in debugging the problem.<div><br></div><div>This is now being tracked as:</div><div><br></div><div><a href="https://jira.lsstcorp.org/browse/DM-1725">https://jira.lsstcorp.org/browse/DM-1725</a><br></div><div><br></div><div>I've put it on my stack for now, but that's no guarantee I'll get to it terribly soon.</div><div><br></div><div><br></div><div>Jim</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 20, 2014 at 5:12 PM, <span dir="ltr"><<a href="mailto:darko@aob.rs" target="_blank">darko@aob.rs</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi folks.<br>
<br>
meas_base and meas_algorithms are not able to do tests on OpenSuse13.1 with gcc version 4.8.1 20130909 [gcc-4_8-branch revision 202388] (SUSE Linux)<br>
<br>
Reason is to agresive optimization (-O3). -O2 doesn't work either, but I can report success with -O1. So the recipe is as follows<br>
<br>
when<br>
eups distrib install -t v10_0 lsst_distrib<br>
<br>
crashes on meas_base - open a new terminal, go to you install directory, do loadLSST.bash (or whatever).<br>
change directory to $Instal_directory/<u></u>EupsBuildDir/Linux64/meas_<u></u>base-10.0+2/<br>
<br>
do<br>
<br>
export SCONSFLAGS='opt=1'<br>
<br>
end do all the setups from build.sh - namely<br>
<br>
setup --just --type=build apr 1.3.3.lsst2<br>
setup --just --type=build cfitsio 3360.lsst1<br>
setup --just --type=build doxygen 1.8.5<br>
setup --just --type=build eigen 3.2.0<br>
setup --just --type=build fftw 3.3.3<br>
setup --just --type=build gsl 1.16.lsst1<br>
setup --just --type=build minuit2 5.28.00<br>
setup --just --type=build mysql 5.1.65.lsst1<br>
setup --just --type=build mysqlclient 5.1.73.lsst1<br>
setup --just --type=build python 0.0.2<br>
setup --just --type=build sqlite 3080200<br>
setup --just --type=build swig 3.0.2.lsst1<br>
setup --just --type=build xpa 2.1.15.lsst1<br>
setup --just --type=build apr_util 1.3.4.lsst2<br>
setup --just --type=build boost 1.55.0.1.lsst2<br>
setup --just --type=build mysqlpython 1.2.3+13<br>
setup --just --type=build numpy 0.0.1+2<br>
setup --just --type=build scons 2.3.0+1<br>
setup --just --type=build wcslib 4.14+7<br>
setup --just --type=build activemqcpp 3.5.0+15<br>
setup --just --type=build astrometry_net 0.50.1+3<br>
setup --just --type=build matplotlib 0.0.1+2<br>
setup --just --type=build pyfits 3.2.4.lsst1<br>
setup --just --type=build scisql 0.3.4+2<br>
setup --just --type=build sconsUtils 10.0<br>
setup --just --type=build astrometry_net_data 10.0+1<br>
setup --just --type=build base 10.0+2<br>
setup --just --type=build geom 10.0+1<br>
setup --just --type=build lsst 10.0<br>
setup --just --type=build lsst_thirdparty 10.0+2<br>
setup --just --type=build ndarray 10.0+1<br>
setup --just --type=build pex_exceptions 10.0+1<br>
setup --just --type=build utils 10.0+1<br>
setup --just --type=build daf_base 10.0+2<br>
setup --just --type=build pex_logging 10.0+1<br>
setup --just --type=build pex_policy 10.0+1<br>
setup --just --type=build daf_persistence 10.0+2<br>
setup --just --type=build pex_config 10.0+1<br>
setup --just --type=build afw 10.0+3<br>
setup --just --type=build cat 10.0+2<br>
setup --just --type=build lsst_libs 10.0+2<br>
setup --just --type=build ctrl_events 10.0+4<br>
setup --just --type=build ctrl_provenance 10.0+5<br>
setup --just --type=build shapelet 10.0+2<br>
setup --just --type=build skymap 10.0+2<br>
setup --just --type=build skypix 10.0+2<br>
setup --just --type=build daf_butlerUtils 10.0+3<br>
setup --just --type=build pex_harness 10.0+7<br>
setup --just --type=build ctrl_orca 10.0+8<br>
setup --just --type=build obs_test 10.0+2<br>
setup --just --type=build ctrl_execute 10.0+8<br>
setup --just --type=build pipe_base 10.0+2<br>
setup --just --type=build testing_endtoend 10.0+7<br>
setup --just --type=build coadd_utils 10.0+3<br>
setup --just --type=build ctrl_platform_gordon 10.0+8<br>
setup --just --type=build ctrl_platform_lsst 10.0+8<br>
setup --just --type=build coadd_chisquared 10.0+3<br>
<br>
<br>
after that change directory to<br>
<br>
$Instal_directory/<u></u>EupsBuildDir/Linux64/meas_<u></u>base-10.0+2/meas_base-10.0+2<br>
<br>
and do<br>
<br>
setup --type=build -k -r<br>
<br>
./ups/eupspkg VERBOSE=0 FLAVOR=Linux64 config<br>
./ups/eupspkg VERBOSE=0 FLAVOR=Linux64 build<br>
./ups/eupspkg VERBOSE=0 FLAVOR=Linux64 install<br>
<br>
<br>
If everything goes fine then from your original terminal/window do<br>
<br>
eups declare meas_base 10.0+2 -r $Instal_directory/Linux64/<u></u>meas_base/10.0+2 -t current<br>
<br>
eups declare meas_base 10.0+2 -r $Instal_directory/Linux64/<u></u>meas_base/10.0+2 -t v10_0<br>
<br>
restart instalation<br>
<br>
<br>
Now, meas_algorithms will probably die as well (same recipe):<br>
<br>
In terminal you were using to manualy build go to $Instal_directory/<u></u>EupsBuildDir/Linux64/meas_<u></u>algorithms-10.0+2<br>
<br>
do just one new setup (others are already done)<br>
<br>
setup --just --type=build meas_base 10.0+2<br>
<br>
change directory to<br>
<br>
$Instal_directory/<u></u>EupsBuildDir/Linux64/meas_<u></u>algorithms-10.0+2/meas_<u></u>algorithms-10.0+2<br>
<br>
do<br>
<br>
setup --type=build -k -r<br>
<br>
./ups/eupspkg VERBOSE=0 FLAVOR=Linux64 config<br>
./ups/eupspkg VERBOSE=0 FLAVOR=Linux64 build<br>
./ups/eupspkg VERBOSE=0 FLAVOR=Linux64 install<br>
<br>
<br>
Now from the original terminal do eups declare step<br>
<br>
eups declare meas_base 10.0+2 -r $Instal_directory/Linux64/<u></u>meas_algorithms/10.0+2 -t current<br>
<br>
eups declare meas_base 10.0+2 -r $Instal_directory/Linux64/<u></u>meas_algorithms/10.0+2 -t v10_0<br>
<br>
<br>
and restart installation (this should go smoothly till the end)<br>
<br>
Hope this helps in sorting out problems with meas_base and meas_algorithms on other distributions as well.<br>
<br>
Someone should check why this happens and maybe offer more elegant solution...<br>
<br>
Cheers<br>
D.<span class=""><br>
<br>
<br>
On Tue, 9 Dec 2014, Mario Juric wrote:<br>
<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Hi Mike,<br>
CentOS 6 is supported (it's out default/reference platform). What problem are you seeing building on CentOS?<br>
--<br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.<br>
<br>
On December 8, 2014 3:55:51 PM PST, Mike Lund <<a href="mailto:mike.lund@gmail.com" target="_blank">mike.lund@gmail.com</a>> wrote:<br>
Thanks for all that information, at the present I have the poor luck of the other machine I've got access to running CentOS 6.6, which is also not supported at this time, so I'll be<br>
watching for support being extended to Ubuntu 14.04 or CentOS 6.6 so that I can complete and installation and resume working with MAF again.<br>
<br>
I'm definitely also willing to try out any other distribution methods that are being explored as a guinea pig of sorts, although from looking at CernVM-FS, it seems like Fabio<br>
wouldn't have much need of that for that implementation.<br>
<br>
- Mike Lund<br>
<br>
On Mon, Dec 8, 2014 at 1:27 PM, Dominique Boutigny <<a href="mailto:boutigny@in2p3.fr" target="_blank">boutigny@in2p3.fr</a>> wrote:<br>
Hi Mike,<br>
<br>
I am also using a Ubuntu 14.04 system and I am having the same problem as you. So, what I am doing is to build the stack on another platform (I use Scientic Linux / Redhat)<br>
and simply make a tar ball that I deploy on my system. This is working very well, you only have to fix a couple of things for eups.<br>
Here is a copy of the recipe I put in the IN2P3 wiki : <a href="http://lsst.in2p3.fr/wiki/index.php/Calcul" target="_blank">http://lsst.in2p3.fr/wiki/<u></u>index.php/Calcul</a> (you can create an account for yourself, it is not moderated).<br>
<br>
Hope this helps<br>
<br>
Dominique<br>
<br>
PS : Fabio Hernandez at CC-IN2P3 is also working on a system to deploy the LSST stack using CernVM-FS. This is very convenient. You can contact him directly if you wish.<br>
<br></span>
INTRODUCTION<span class=""><br>
<br>
It is possible to replicate a working stack installation into another directory structure or even on another computer without recompiling the packages. Here is how to proceed,<br>
taking the example of the stack v9_2 installed at CC-IN2P3 :<br>
<br>
cd /sps/lsst/Library/stack_v9_2<br>
tar -cvzf stack.tar.gz *<br>
<br>
cp stack.tar.gz some_directory (on the same or on another server)<br>
<br>
tar -xvzf stack.tar.gz<br>
<br>
At this stage we have the stack directory structure but in order to make it work, we need to fix the following :<br>
<br></span>
o Cleanup any LSST or EUPS environment variable (it may be safer to start a completely new shell)<br>
o Change LSST_HOME in loadLSST.sh<br>
o Change EUPS_DIR and EUPS_PATH in eups/bin/setups.sh<span class=""><br>
<br>
Then one can now re-initialize the stack environment :<br>
<br>
source loadLSST.sh<br>
<br>
The eups database should now be ok.<br>
<br></span>
[MODIFIER]CAVEATS<span class=""><br>
<br>
[modifier]Fixing eups for some manually declared packages<br>
<br>
If some packages have been manually declared to eups without specifying a path relative to EUPS_PATH, one have to undeclare those packages in order to re-declare them with the<br>
right path. For instance :<br>
<br>
unsetup obs_cfht my_obs_cfht<br>
eups undeclare obs_cfht my_obs_cfht<br>
eups declare -r some_directory/my_packages/<u></u>obs_cfht obs_cfht my_obs_cfht<br>
setup obs_cfht my_obs_cfht<br>
<br>
[modifier]Fixing ipython<br>
<br>
If the stack release comes with the anaconda python distribution, the firs line of the ipython wrap-up script should be fixed to point to the right python path.<br>
<br></span>
[MODIFIER]REMARK<div><div class="h5"><br>
<br>
This method is working to install the stack on Ubuntu 14.04 by copying the stack from a SL6.5 distribution<br>
<br>
On 12/08/2014 11:17 AM, Mike Lund wrote:<br>
Dominique, thanks for the quick answer on this.<br>
<br>
To follow this up with a probably naive question, are there any options to get this working other than the stack build? If it effects anything, my needs for the software<br>
are primarily just for writing new metrics for the MAF. I also know that Ubuntu 14.10 is out now, and that is something that I could upgrade to if the issues with gcc<br>
are limited to just 14.04 and not later versions.<br>
- Mike Lund<br>
<br>
On Sat, Dec 6, 2014 at 1:12 PM, Dominique Boutigny <<a href="mailto:boutigny@in2p3.fr" target="_blank">boutigny@in2p3.fr</a>> wrote:<br>
Hi Mike,<br>
<br>
Until recently, the stack build was incompatible with Ubuntu 14.04 due to some gcc subtleties. So, unless this was fixed in the mean time, this is likely the<br>
reason of the errors that you are seeing.<br>
<br>
Best,<br>
<br>
Dominique<br>
On 12/6/2014 11:03 AM, Mike Lund wrote:<br>
Hello, Lynne Jones recommended I send this question to here and thanks in advance for any help.<br>
<br>
I'm trying to install the LSST software, and my install is failing when trying to meas_base, and the screen output is saying that it's running python test<br>
scripts and failing 15 tests. I'm trying to install this on Ubuntu 14.04.1 LTS, and the last few lines output to terminal are the following:<br>
<br>
scons: *** [checkTestStatus] Error 1<br>
scons: building terminated because of errors.<br>
+ exit -4<br>
eups distrib: Failed to build meas_base-master-g5cbca8985d.<u></u>eupspkg: Command:<br>
source /home/mike/lsst/eups/bin/<u></u>setups.sh; export EUPS_PATH=/home/mike/lsst; (/home/mike/lsst/EupsBuildDir/<u></u>Linux64/meas_base-master-<u></u>g5cbca8985d/build.sh) >><br>
/home/mike/lsst/EupsBuildDir/<u></u>Linux64/meas_base-master-<u></u>g5cbca8985d/build.log 2>&1 4>/home/mike/lsst/<u></u>EupsBuildDir/Linux64/meas_<u></u>base-master-g5cbca8985d/build.<u></u>msg <br>
exited with code 252<br>
<br>
I've also attached the build.log for this.<br>
<br>
- Mike Lund<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
dm-users mailing list<br>
<a href="mailto:dm-users@lists.lsst.org" target="_blank">dm-users@lists.lsst.org</a><br>
<a href="https://lists.lsst.org/mailman/listinfo/dm-users" target="_blank">https://lists.lsst.org/<u></u>mailman/listinfo/dm-users</a><br>
<br>
<br>
-- <br>
Dominique Boutigny - CNRS / CC-IN2P3<br>
Now at SLAC National Accelerator Laboratory<br>
<br>
Mail : <a href="mailto:boutigny@in2p3.fr" target="_blank">boutigny@in2p3.fr</a> - <a href="mailto:boutigny@slac.stanford.edu" target="_blank">boutigny@slac.stanford.edu</a><br>
Office : <a href="tel:%2B1%20650-926-5759" value="+16509265759" target="_blank">+1 650-926-5759</a> - Cellular : <a href="tel:%2B1%20774-232-0912" value="+17742320912" target="_blank">+1 774-232-0912</a> <br>
______________________________<u></u>_________________<br>
dm-users mailing list<br>
<a href="mailto:dm-users@lists.lsst.org" target="_blank">dm-users@lists.lsst.org</a><br>
<a href="https://lists.lsst.org/mailman/listinfo/dm-users" target="_blank">https://lists.lsst.org/<u></u>mailman/listinfo/dm-users</a><br>
<br>
<br>
<br>
-- <br>
Dominique Boutigny - CNRS / CC-IN2P3<br>
Now at SLAC National Accelerator Laboratory<br>
<br>
Kavli Building - Room 221<br>
Mail : <a href="mailto:boutigny@in2p3.fr" target="_blank">boutigny@in2p3.fr</a> - <a href="mailto:boutigny@slac.stanford.edu" target="_blank">boutigny@slac.stanford.edu</a><br>
Office : <a href="tel:%2B1%20650-926-5759" value="+16509265759" target="_blank">+1 650-926-5759</a> - Cellular : <a href="tel:%2B1%20774-232-0912" value="+17742320912" target="_blank">+1 774-232-0912</a><br>
<br>
<br></div></div>
______________________________<u></u>______________________________<u></u>______________________________<u></u>______________________________<u></u>______________________________<u></u>______________________________<u></u>_____________<span class=""><br>
dm-users mailing list<br>
<a href="mailto:dm-users@lists.lsst.org" target="_blank">dm-users@lists.lsst.org</a><br>
<a href="https://lists.lsst.org/mailman/listinfo/dm-users" target="_blank">https://lists.lsst.org/<u></u>mailman/listinfo/dm-users</a><br>
<br>
<br>
</span></blockquote>
<br>_______________________________________________<br>
dm-users mailing list<br>
<a href="mailto:dm-users@lists.lsst.org">dm-users@lists.lsst.org</a><br>
<a href="https://lists.lsst.org/mailman/listinfo/dm-users" target="_blank">https://lists.lsst.org/mailman/listinfo/dm-users</a><br></blockquote></div><br></div>