I would like to upgrade my PCL to a newer version to fix a problem I have with QHull related to this issue.
I'm on ubuntu so I installed PCL with sudo apt install libpcl-dev but I can only get the version 1.10.1. How can I install a newer version ?
The problem is apparently fixed by this commit. It's in the tag 1.12.1.
I know that in theory I can use cmake and build my own PCL but from what I saw with the apt install, there is a huge amount of dependencies + I will also need this particular Qhull version that they mention in the issue and commit... I'm not sure I can make this work without the package manager. Any leads on this problem ?
Thanks !
In its simplest form, building and installing PCL goes likes this:
Clone the GitHub repo and cd inside it
Optionally checkout a git tag or stay on the master branch (default)
mkdir build && cd build
Run cmake with cmake ..
Build and install with make -j2 && sudo make install
For more information, see here: https://pcl.readthedocs.io/projects/tutorials/en/master/compiling_pcl_posix.html
When you previously had libpcl-dev installed, you can remove that package without (auto-)removing the dependencies, then you should have most if not all dependencies required for building from source already installed.
You didn't say which Ubuntu version you use, but judging from the version of libpcl-dev, I assume it is focal (20.04). The Qhull version installed there is fine, it already has a reentrant interface.
Related
We need to install R-base version 3.5+ on an offline machine running SLES12.3
We have downloaded all the packages from the the SUSE r repo
http://download.opensuse.org/repositories/devel:/languages:/R:/released/openSUSE_12.3/x86_64/
while running zypper install on the packages there are additional dependencies that we are not able to find the relevant packages to download.
These include:
libtcl8.5.so()(64bit)
libgomp.so.l()(64bit)
But we are not able to find the dependency package that include these libraries.
What should be the correct approach for installing these libraries offline? where can we find these libraries?
Is there a better way for offline installing R-base ? we tried to follow the instructions on the cran rstudio page
The files you downloaded don't match the distribution you're running. SUSE Linux Enterprise (SLE) and openSUSE are similar in some ways, but these are really two separate distributions and you can not always mix binaries between the two. To install R on SLE Server 12.3, you should use the repository https://download.opensuse.org/repositories/devel:/languages:/R:/released/SLE_12/.
You can find out these URLs by looking at the right hand-side column at https://build.opensuse.org/project/show/devel:languages:R:released. Look for things called "SLE" there.
Install the Development Tools, according to this answer
zypper install --type pattern Basis-Devel
Download R source and install it
wget http://cran.univ-paris1.fr/src/base/R-3/R-3.5.0.tar.gz
tar zxf R-3.5.0.tar.gz
cd R-3.5.0
./configure --enable-R-shlib
make
make check
make install
Maybe there are still dependencies missing, which need to be installed with zypper (I don't have any Suse to try myself). With this method you have an "empty" R and you will install R packages one by one (with R CMD INSTALL). Maybe not the best answer for your need, but an answer.
I follow the instructions to install meteor 1.6 on Windows(10) as stated on Meteor.com (choco install meteor) and it's installed a meteor v0.0.2 ?
When I try to run any meteor command I get: bash: meteor: command not found
and when I try choco upgrade meteor I get:
$ choco upgrade meteor
Chocolatey v0.10.8
Upgrading the following packages:
meteor
By upgrading you accept licenses for the packages.
meteor v0.0.2 is the latest version available based on your source(s).
Chocolatey upgraded 0/1 packages.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
I tried choco uninstall meteor and then reinstall choco instlal meteor but same issue. Searching around online a little I found this page:
https://chocolatey.org/packages/meteor
I do have meteor installed and running on version 1.6.0.1 on Window 10's Ubuntu bash which was installed via curl https://install.meteor.com/ | sh
Following on from above post https://stackoverflow.com/a/47967277/642729 by Gary Ewan Park. The below comment on https://chocolatey.org/packages/meteor clarifies the Chocolately/Meteor versioning
The current version of Meteor is 1.6;
is this the version in the 0.0.2 Chocolatey package?
[Garrie Powers • 2 months ago]
The version number of the Chocolatey package is the version of the installer.
Meteor is unique in the way it works in that all versions
are capable of springboarding to other versions.
Therefore, in the same way as the Unix installer installs the latest version,
the Chocolatey installer will always install the latest version.
So at this exact moment, the answer to your question is "yes"!
[Jesse Rosenberger Garrie Powers • 2 months ago]
The best advice would be to reach out to the maintainers of that package of chocolatey.org. This can be done by clicking on the "Contact Maintainers" link of this page:
https://chocolatey.org/packages/meteor
It would seem that the creators of the application, also own the Chocolatey package, so hopefully they will get back to you.
From the official installer github:
The version of this Meteor installer is not to be confused with Meteor itself. Meteor, once installed, will always "springboard" to (download, install and run) the correct version of Meteor necessary for the application being executed.
...
When necessary, specific versions of Meteor can be installed using
Chocoloatey's --params argument which will download that specific
version from Meteor's installation server. For example, to install
Meteor 1.5.4.4:
C:> choco install meteor --params="'/RELEASE:1.6.0.1'"
Note: Prior to
Meteor 1.6, 64-bit versions were not available. Therefore, in order to
install versions prior to Meteor 1.6, you'll also need to pass
Chocolatey's --x86 option when running choco install on 64-bit Windows
platforms. For example:
C:> choco install meteor --x86 --params="'/RELEASE:1.5.4.4'"
Now a bit of background of my current setup:
I have Python3.3 running on Centos 6. I'm currently working on a web application using Flask that runs on Apache 2.2.15 with mode WSGI 4.5.3 and virtualenv 15.0.2.
pip --version pip 8.1.2 from /usr/local/bin/lib/python3.3/site-packages (python 3.3)
I have installed pysvn with pip and when I run pip show pysvn says
Location: /usr/local/bin/lib/python3.3/site-packages
755 permissions recursively set to /usr/local/bin/lib/python3.3/site-packages. And I passed --system-site-packages argument to virtualenv to use the global site packages.
Even when I try to import the package from python interpreter it does not work. So it is not specific to my virtualenv setup but rather a global problem.
I must mention that other packages installed with pip work perfectly fine (i.e. flask).
I've exhausted all other avenues before coming forward to you guys. Any suggestion would be highly appreciated as I ran out of ideas.
L.E.
I did manage to install it in the end. I'm not completly sure yet why and how but I presume is was compatibility issue.
First of all I have uninstalled svn 1.6+ and installed version 1.8.16 instead which seems to be tested against the latest two versions.
Second, I have uninstalled the troublesome pysvn instance and installed pysvn-1.8.0 workbench "sudo /var/www/FlaskApp/FlaskApp/flask/bin/pip install pysvn-1.8.0.tar.gz". In this case I have installed it my local environment. The 1.9.0 version of pysvn did not work.
L.L.E.
False positive, still doesn't work. I'm going to interact with svn via command line from my script.
L.L.L.E.
After installing svn 1.8.16 and svn-devel along with the rest of dependencies described in the readme file I have managed to successfully install it from the source fallowing the instructions.
Thanks for your help Barry.
pysvn is not available from PyPI because PyPI has no way to allow me to upload pysvn for each supported SVN version. Let alone deal with the issues of installing on a Linux distro given the choices for pysvn dependencies.
(APR, SVN, OpenSSL etc).
Fedora packages pysvn for the Fedora release.
I'm assuming that means it is on RHEL and therefore packaged by CentOS.
(But I do not have RHEL or CentOS to check this on)
If you find that a package is not available for your CentOs is not hard
to build pysvn on a linux distro. Get the source kit and follow the readme.html should get you going.
Barry (pysvn maintainer)
Suddenly today, without us changing any configuration, all test containers began to fail because of the following error:
$ sudo -E apt-get -yq --no-install-suggests --no-install-recommends --force-yes install libqt5webkit5-dev qtdeclarative5-dev
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package libqt5webkit5-dev
E: Unable to locate package qtdeclarative5-dev
We have the following configuration in our .travis.yml in order to use QT5 on Travis with Ubuntu 12.04:
apt:
sources:
- ubuntu-sdk-team
packages:
- libqt5webkit5-dev
- qtdeclarative5-dev
We've tried to fix this but are baffled. Any ideas? Anyone else experiencing this?
We had the same problem and after contacting Travis support I learned that apparently the ubuntu-sdk-team has stopped providing packages for Precise and you need to switch dist to Trusty. In order to get the builds working again add this to your .travis.yml file
sudo: required
dist: trusty
You can read more about it here
Ubuntu 12.04 will be deprecated in less than a year from now (exactly at 2017-04-26), and also Qt Webkit is deprecated with the new versions of Qt starting from Qt 5.5. It is removed in Qt 5.6 from the Qt distribution:
With 5.6, Qt WebKit and Qt Quick 1 will no longer be supported and are
dropped from the release. The source code for these modules will still
be available. You can continue to compile and use these modules, but
we will not be supporting them any longer.
http://blog.qt.io/blog/2016/03/16/qt-5-6-released/
So, you in order to maintain the stability of your development environment, either you have to stay with the current versions of Ubuntu and Qt (which has its own issues), or you have to port your code to work with the newer versions of Ubuntu and Qt, like Qt 5.5 on Ubuntu 16.04 LTS.
My R version is 2.7.1 (on Debian) and some packages are asking for > 2.10. I cannot find updating instructions and I don't want to remove and reinstall as I have other things depending on R and I don't want to mess up. Is there an update procedure?
Closest thing to my problem is on this thread.
check out the instructions for installing from source. Its easy on a Linux box, and you can do the install in any directory you like, you dont even need superuser permissions. Once compiled you can even run R from that directory without messing up any system-installed R. As long as you give the full path to R's binary, or put the path to it in your PATH environment variable, when starting it it will work fine.
FYI
It seems that R on Debian with versions previous to 2.7.1 cannot be updated.
The current core runs from 2.7.1 up. The only way to do it is to remove the existing version.
As this was not straight forward I post it here. If you have Rapache or other things connecting to R disable them with dismode or related.
apt-get purge r-base r-base-dev
I had to do this as well
dpkg -P r-base-core
until this shows no more installed R packages
dpkg -l r-*
Then follow the instruction from http://cran.r-project.org/bin/linux/debian/, with the amendment that you should use deb instead of deb-src in /etc/apt/sources.list.
deb http://<favorite-cran-mirror>/bin/linux/debian lenny-cran/
Before installing run this and it should not say 2.7.1.
apt-cache policy r-base-dev