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 > > Looks like it is linking to /lib/libgcc_s.so.1 and should use > /usr/local/lib/gcc47/libgcc_s.so.1, am I right?
#1, you rock. #2, you are right. Is it possible that math/p-numpy fails to use LDFLAGS which would have added -Wl,rpath=/usr/local/lib/gcc47/libgcc_s.so.1 when linking? Or is it a question of getting the order of the dynamic library search paths right? Unfortunately I am far from an expert in this area (and having two libraries with the same version, one of which is a superset, is tricky). (Why is this not happening when building with lang/gcc being GCC 4.6 or lang/gcc46, though? That puzzles me. Also, if this were a general issue, wouldn't all ports using Fortran be affected?) Can you somehow fix this in/for math/p-numpy? Gerald _______________________________________________ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"