Date: Wed, 10 Sep 2014 18:07:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193531] New: New port: cad/elmerfem Message-ID: <bug-193531-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193531 Bug ID: 193531 Summary: New port: cad/elmerfem Product: Ports Tree Version: Latest Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: pfg@FreeBSD.org Created attachment 147181 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147181&action=edit shar generated script for cad/elmerfem port We lost science/elmer-fem after a series of gcc updates and the disappearance of g77. In the meantime the distribution of the upstream package has changed and it is not available as individual packages anymore. I am attaching a unified cad/elmerfem port which replaces the left overs from the old elmer package: math/elmer-umfpack science/elmer-eio science/elmer-matc science/elmer-meshgen2d science/elmergrid We are now building this package very closely to what upstream suggests, with the side-effect that the individual components are configured, built and installed in chain. This sort-of works better with staging than before. The original package doesn't follow hier(7) strictly so it is installed in ${PREFIX}/elmer, just as upstream does. Unlike upstream, we use the existing ports for lapack, arpack and blas. Also tricky is that while portlint suggests we don't need to set CFLAGS and CXXFLAGS for CONFIGURE_ENV, removing them breaks the port. A final note is that we fail check-plist but the auto-package plist seems to work fine (fix/enhancements welcome). -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193531-13>