-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error building from source, looks blitz related: Ubuntu 14.04.3 #868
Comments
Could you do a |
Should look like this BTW:
...but there was a 0.11 package floating around the repos that's actually an older blitz which would cause the above error. |
|
Yep that's the culprit. Purge it, then But before you do, can you try |
So I can apt-get remove plus the package names that dpkg returned? |
I think this is an old system and got it from ska-sa ppa when it was still I removed all packages from ska-sa ppa just to be sure.
|
You should apt-get remove the blitz packages, then apt-get update just to be sure, then apt-get install libblitz0-dev. Check the output to make sure that 1:0.10 is being installed not 1:0.11. If it still gets 1:0.11 somewhere, then @gijzelaerr needs to do some more scouring of the repos... |
OK it's installed 1:0.10 across the board from your method. Rebuilding now... Thanks. |
Let us hope 1:0.11 has been properly Stalinized from all repositories. |
Can confirm that this works. I've also edited the suggested .bashrc items on the building from source page which didn't reflect current paths. |
Excellent, thanks! On Wed, Sep 2, 2015 at 4:40 PM, IanHeywood notifications@github.com wrote:
|
Likewise! Cheers. |
I recently went through the exercise of building casacore. casarest, lwimager, and wsclean on the Cambridge supercomputer. Only took about 4 days of headbanging to get things right. The final joke of course was that using a supercomputer doesn't help that much because of remote disk I/O issues with CASA measurement sets. A wsclean that took about 1.5 hours on my laptop timed out after 5 hours wallclock time on the Cambridge computer. Sigh. |
Apologies for the slightly off topic message. I’ve been compiling the same stack recently and had similar issues. But seriously this email MADE MY DAY!!! ROTFL!!!
|
Up to the 'Building the software' section on this page. Brace yourselves...
The text was updated successfully, but these errors were encountered: