No apparent problems ./contrib/fixup-libgfortran.sh /home/vagrant/julia/julia-cb77503114/lib/julia ‘/lib/x86_64-linux-gnu/libgcc_s.so.1’ -> ‘/home/vagrant/julia/julia-cb77503114/lib/julia/libgcc_s.so.1’ ‘/usr/lib/x86_64-linux-gnu/libgfortran.so.3’ -> ‘/home/vagrant/julia/julia-cb77503114/lib/julia/libgfortran.so.3’ ‘/usr/lib/x86_64-linux-gnu/libquadmath.so.0’ -> ‘/home/vagrant/julia/julia-cb77503114/lib/julia/libquadmath.so.0’ Found traces of libgfortran/libgcc in /lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu
But libgfortran doesn’t appear in the tar file anywhere. make install doesn’t put it in a lib folder anywhere either. On June 25, 2015 at 4:04:23 PM, Elliot Saba ([email protected]) wrote: Hmmm, well, it should, so that's worrying that it's not doing so on your system. When you run `make binary-dist`, you the makefile should run a script called `fixup-libgfortran.sh`, which does exactly what you want. Here is an example log of what it should look like when you run `make binary-dist`, the important part of which is: ./contrib/fixup-libgfortran.sh /home/centos/buildbot/slave/package_tarball64/build/julia-1e081b79ed/lib/julia `/home/centos/local/lib64/libgcc_s.so.1' -> `/home/centos/buildbot/slave/package_tarball64/build/julia-1e081b79ed/lib/julia/libgcc_s.so.1' `/home/centos/local/lib64/libgfortran.so.3' -> `/home/centos/buildbot/slave/package_tarball64/build/julia-1e081b79ed/lib/julia/libgfortran.so.3' `/home/centos/local/lib64/libquadmath.so.0' -> `/home/centos/buildbot/slave/package_tarball64/build/julia-1e081b79ed/lib/julia/libquadmath.so.0' Found traces of libgfortran/libgcc in /home/centos/local/lib64 ./contrib/fixup-libstdc++.sh /home/centos/buildbot/slave/package_tarball64/build/julia-1e081b79ed/lib/julia `/home/centos/local/lib64/libstdc++.so.6' -> `/home/centos/buildbot/slave/package_tarball64/build/julia-1e081b79ed/lib/julia/libstdc++.so.6' This is showing how it finds and installs libgfortran.so.3, you should see something similar in your installs as well. This should run as long as you're not running on windows, so there must be some kind of error happening that is hopefully printed out to the console. -E
