Installing Julia BinaryBuilder.jl packages on Windows 7 - windows

I am having difficulty installing various Julia packages on my Windows 7 laptop. When trying to add certain packages I receive the following error:
(v1.3) pkg> add MbedTLS
Updating registry at `C:\Users\uname\.julia\registries\General`
Updating git-repo `https://github.com/JuliaRegistries/General.git`
Resolving package versions...
ERROR: Unable to automatically install 'MbedTLS' from 'C:\Users\uname\.julia\packages\MbedTLS_jll\wUtL4\Artifacts.toml'
Several packages install happily, and I think I've narrowed it down to those that are supplied via BinaryBuilder.jl, such as MbedTLS, Arpack, OpenSpecFun. If I try to install any packages that have any such packages as a dependency I get the same error message when it hits one of these (initially encountered when I was trying to install Genie.
I am using the latest Julia (1.3.1), although I encountered the same issue previously in 1.2 - I managed to fix things eventually in that case, and tried a similar approach (manually downloading and placing in packages folder) but have not been able to fix things in this instance (although I confess that my notes were a little lacking so can't be certain I'm doing the correct thing). The various packages seem to exist in ...\.julia\packages\ (although not in .julia\compiled), but julia complains whenever I try to add them to some environment.
I don't think I understand julia's package system well enough to see quite what is going on here. I have seen other people with similar issues but not found anything yet which has worked - any help would be much appreciated!

This usually is due to an issue with your powershell installation, which is what we use to download these binaries in Julia 1.3 and 1.4. In particular, most of the internet (including GitHub, where most of our binaries are hosted) disabled SSL v3, TLS 1.0, and TLS 1.1 in 2018. Windows 7 is old enough that it doesn't speak TLS 1.2+ natively; instead you must install two packages:
This TLS easy_fix
Windows Management Framework 3.0 or later, to get Powershell v3+
This is necessary on Windows 7, but not on Windows 10. For more instructions, you can read the Julia platform specific instructions: https://julialang.org/downloads/platform/

Related

Manage multiple terraform binaries on macOS

I'm facing an issue with some providers which are not compatible with terraform-Arm64.
For example - the Spotinst provider, so I switched the terraform binary installed on my MacOS to terraform-Amd64 as they consulted me to do, and then everything seemed to work fine.
But after, it caused errors with other providers which worked with my previous installation of terraform-Arm64.
I have an Apple M1 Pro chip, and I currently installed both of the binaries and called one of the commands terraform-arm and the other terraform-amd.
I switch between them when necessary, but I'm not sure that this is the right way to manage it.
Do you know any other ways to use both of the downloads?

How can I install Bugzilla on OS X without duplicating TeXlive?

This answer convincingly argues that there is no way to determine the storage needed to install a MacPorts package.
Also, as is clear from this Q & A it's a bad idea to install TeXlive using MacPorts since it becomes difficult to maintain it. It's much better to install an external TeXlive.
MacPorts has a recipe for installing Bugzilla, but during a dryrun (-y) I see texlive-bin in the list of packages Bugzilla depends on, which means that it will be duplicated.
Is there a way to install Bugzilla on a Mac (with or without MacPorts) without duplicating TeXlive?
Interesting. port rdeps --no-build bugzilla[1] shows no texlive-bin or any other tex-related ports that I'm aware of. I don't know that much about bugzilla but I can't imagine why it needs tex.
However, we have no maintainer for the bugzilla port. MacPorts is at version 4.4.5 whereas the current release is 5.0.3. It is also using MySQL version 5.1 which is getting pretty old. I wouldn't mind helping but it will be at least a few days before I could take a look at this. You might file a ticket with MacPorts requesting the update.
https://trac.macports.org/wiki/Tickets
There is already a ticket regarding the database issue:
https://trac.macports.org/ticket/43431

scidb installation on single debian server

I would like to try scidb as a replacement for hdf5. I would like to test it on my Debian laptop (no clusters) to give it a try.
Is this possible? Might be that Debian (as opposed to Ubuntu) is not supported?
I had no luck with the installation instructions. The deployment script tells that my OS is not supported. The scidb userguide says about some pre-built packages (for Ubuntu, at least). But there is no hint on how to obtain them.
SciDB is limited to RedHat / CentOS, and to Ubuntu as of the 14.9 release. Folk who want to run it on other distros generally compile from code.
Information about how to obtain the sources (as well as current documentation and community discussion) can be found on the forums here ... http://www.scidb.org/forum/. You'll need to register as a forum user.
Specifically, have a look at http://www.scidb.org/forum/viewtopic.php?f=16&t=364. There's a list of releases and links to code bundles there.
I installed SciDB several times using several ways (building from sources and installing from packages, installing the cluster version and the dev version).
Installation from packages
First, if you choose to install from packages (the easiest and fastest way), SciDB is very very sensitive about your Linux version. For example, for the last version of SciDB (14.8), if you choose to install on a Ubuntu, it has to be a Ubuntu 12.04 (and not a 14.04, a common mistake) 64 bits (meaning you have to install the AMD64 version even if you have an Intel processor). It won't work if you have a different version.
If you have an Ubuntu 12.04 AMD64, Paradigm4 provides a deployment script and a documentation with very simple steps:
https://github.com/Paradigm4/deployment
Installation from sources
It's not so difficult but it can be painful and time consuming. I did it because we had to compile a custom plugin for SciDB. You have two types of installation: dev install (in SciDB user directory) and cluster install (in /opt/ directory).
You have to be registered on their forum to have the link to the source code. They provide a specific documentation to build from source.
Good luck.
Several months ago I have dealt with porting SciDB 14.12 to an unsupported Linux - Fedora 19. If your OS is not supported, it will neither be supported if you try to install from the sources. You have to start from the sources, but then you have to adapt the deployment and installation scripts. The sources can be downloaded from SciDB forum.
Namely, add a new platform to deployment/common/os_detect.sh. Then, there are multiple platform specific deployment scripts, such as deployment/common/prepare_toolchain.sh, deployment/common/prepare_coordinator.sh and deployment/common/prepare_chroot.sh. You need to make sure those prepare the environment as they would on the supported OS'. I used Red Hat 6 and CentOS 6 as a reference, as those are both more similar to Fedora. Since your OS is Debian, you can first try falling back to Ubuntu deployment (in os_detect.sh).
Another problem you may encounter are the 3rd party tools, specially Boost. In my case, I had to build it manually from sources.
Sometimes when porting and debugging it is not convenient to run the scripts with deploy.sh, but it's better to run the deployment scripts directly on the target machine (e.g. coordinator).
Probably the best way to install and to start with SciDB is to download a standard image. With this image you only have to import the virtual machine with a software to virtualize. Moreover there are some characteristics of this virtual machine that are great to develop your first applications.
The main advantage, is that you have an API to SciDB queries and another to R. Then you can explore all options and to test SciDB.
This is the version that I downloaded few months ago: http://www.paradigm4.com/forum/viewtopic.php?f=14&t=1329&sid=606f614e401900cfa750375ba56de656
Nevertheless, there is a problem, the community is too poor. There are little people developing with SciDB.

Install ColdFusion Builder 2 Update 1 Plug-in in Eclipse 4.3

I would like to install ColdFusion Builder 2 Update 1 as a Plug-in for Eclipse 4.3.
The install seems to work without errors but when I attempt to register my license code, I get an error dialog box that says:
"The chosen operation is not enabled."
None of the CFB features appear in Eclipse.
In some of the documentation that I've found it references installing to Eclipse 3.6.
Can CFB 2u1 get installed on Eclipse 4.3? If not, does someone know which version of Eclipse to use for CFB? Hopefully it is something recent or I'm doing something wrong for the install.
I don't know if it matters, but I'm running:
Windows 7 Pro 64-bit
16GB RAM
According to the ColdFusion Builder System Requirements page one needs Eclipse 3.7.1. Having tried to install it on versions later than that, failing, and talking to Adobe about it, they confirmed that one needs that precise version. More recent ones won't do. This is a bit subpar on the part of Adobe, but so be it.

Building v8 on Mac with a 'missing Makefile-x64' error

What references do you know of related to problems with installing and building v8 on Mac and overcoming an error with message something like "missing Makefile-x64"?
Longer version:
I am now over 24 hours in to my attempt at using PyV8 in a python script on OSX. Describing each problem and attempts to fix it would take too long. I suspect the real problem is that up until yesterday I was a Windows user, and my experience installing PyV8 for use in a Python application was painless. But on OS X PyV8 just won't install because v8 was missing, so I install v8 using brew, which still didn't install the ".h" files that PyV8 seemed to want to reference, so I download the v8 source and attempt building it but after solving a dozen other minor issues I just can't seem to get past an error about a Makefile-x64 missing file when I call make native in the v8 source folder. So...
What references do you know of related to this problem?
Related question: https://apple.stackexchange.com/questions/44858/how-to-install-xcode-form-downloaded-package

Resources