Closed nwoods closed 9 years ago
Hi Nate,
Which machine is this? I know I recently compiled 53X_SLC6_Dev - but the differences are minimal between that and the master.
Maria
Login01
I recently compiled master on login06, no idea what is different on the machines.
You could try scram b -v
for some more verbosity maybe?
Here is the error message source
I tried compiling right now from login06. And I get your same error. But, this was working last week. And nobody touched the master, so I am rather puzzled. The login machines are working very bizarrely right now - I wonder if this could be related. Maria
They are acting really weird lately -- has anybody been in touch with Dan et al. about this? I haven't just because I haven't been clever enough to notice consistent enough patterns in their behavior for any debugging to occur.
I copied Devin's most recent area, which is a commit or two behind master, and it compiled fine. What CMSSW did you use? My failing areas were CMSSW_5_3_14_patch2
while his working version was CMSSW_5_3_14
.
I compiled within the last two days on CMSSW_5_3_14
I think you might have it there nate. Dont use the patch. We were using CMSSW_5_3_14, no patch, before.
(And, from past experience, dont go to CMSSW_5_3_2X unless you def. need to, and if you really do tell me because I got it to compile with some work, but I had to kill a few things you will very likely need, on the photons)
Do you get the same error if you compile with scram b -j 1
? Sometimes error messages get scrambled when you run multiple jobs, and the output is misleading.
I don't remember how this was eventually resolved, but it's old and irrelevant now so I'm closing it.
I haven't used master (or anything else in CMSSW_5) in a long time, and honestly haven't really followed the development either, so sorry if my mistake is obvious.
I'm getting an error near the end of the build process on the master branch, it looks like it might be a linker issue?
I build with
At first, I thought this was a fluke caused by my ssh tunnel crashing during a previous compile, but
scram b clean
didn't fix it. I tried deleting the whole release and trying again from scratch, but this gave the same result.pileup_distributions.py
is in the expected folder, so that's not the issue.Anybody know what's going on?