On 23 февр. 2014 г., at 9:48, Gerald Pfeifer ger...@pfeifer.com wrote:
On Thu, 5 Dec 2013, Gerald Pfeifer wrote:
On Wed, 4 Dec 2013, William Grzybowski wrote:
It looks like the build is not respecting FFLAGS, so no -Wl,rpath= for
gfortran. As far as it working for gcc46, it looks like it
On Mon, 24 Feb 2014, Dmitry Sivachenko wrote:
I just committed the patch, thanks for all involved.
Thanks Dmitry, and thinks William for diagnosing the problem
and cooking up that patch to begin with!
Looking forward for final transition to gcc-4.7 in USE_GCC. :)
I just sent an updated patch
On Thu, 5 Dec 2013, Gerald Pfeifer wrote:
On Wed, 4 Dec 2013, William Grzybowski wrote:
It looks like the build is not respecting FFLAGS, so no -Wl,rpath= for
gfortran. As far as it working for gcc46, it looks like it fails to
detect gfortran46 as a compiler and uses gcc46, which respects
On Wed, 4 Dec 2013, William Grzybowski wrote:
It looks like the build is not respecting FFLAGS, so no -Wl,rpath= for
gfortran. As far as it working for gcc46, it looks like it fails to
detect gfortran46 as a compiler and uses gcc46, which respects CFLAGS.
That is, hmm, interesting. =:-)
Hi,
The main reason foe the python failures, if not all, is math/p-numpy.
It is compiling just fine, but the package is not working:
ImportError: /lib/libgcc_s.so.1: version GCC_4.6.0 required by
/usr/local/lib/gcc47/libgfortran.so.3 not found
Looks like it is linking to /lib/libgcc_s.so.1 and
On Wed, 4 Dec 2013, William Grzybowski wrote:
The main reason foe the python failures, if not all, is math/p-numpy.
It is compiling just fine, but the package is not working:
ImportError: /lib/libgcc_s.so.1: version GCC_4.6.0 required by
/usr/local/lib/gcc47/libgfortran.so.3 not found
On Wed, Dec 4, 2013 at 11:13 AM, Gerald Pfeifer ger...@pfeifer.com wrote:
On Wed, 4 Dec 2013, William Grzybowski wrote:
The main reason foe the python failures, if not all, is math/p-numpy.
It is compiling just fine, but the package is not working:
ImportError: /lib/libgcc_s.so.1:
Hi there,
in a different context William Grzybowski wrote If you would like just
assign the port to python@, we would be happy to take more ports. This
is not a new port, but I hope you still can help. :-)
I'd like to move USE_GCC=yes to imply GCC 4.7 instead of GCC 4.6.
Generally this works