Date: Sun, 16 Jan 2022 22:00:34 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 261255] math/nfft: Clean up port (WIP) - Help wanted Message-ID: <bug-261255-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261255 Bug ID: 261255 Summary: math/nfft: Clean up port (WIP) - Help wanted Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: diizzy@FreeBSD.org CC: fernape@FreeBSD.org, marcel@herrbischoff.com, wen@FreeBSD.org Created attachment 231058 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D231058&action= =3Dedit Patch for nfft (WIP) Doing a bit of work fftw3 related ports I noticed that this port pretty much violates all guidelines listed in Porters Handbook so I figured that I shou= ld try to get it in better shape. A few notes,=20 The configure script throws errors if you use something else than bash. The current version pretty much ignores C/LD* flags set and does its own th= ing (including using -march=3Dnative). It sets "-O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-m= ath" compared to "-O2 -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing". There's obviously a difference but are there any opt= ions we should still keep? It now also throws "ld: error: ../../.libs/libnfft3.so: undefined reference= to cexpl" on older versions of FreeBSD (see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216862) and at least fo= r now I can't figure out how it worked before. My current workaround is to link libopenlibm but I don't think that's a great solution or even a correct one. A pair of eyes would be appreciated especially regarding the last issue I've CCed people who've touched this somewhat recently for feedback. --=20 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-261255-7788>