Yes, this looks good - I have been using USE_GCC=11+ for emacs & NATIVECOMP for a few months now with success. Sorry I forgot to submit the change for review - and thanks for picking it up. -- John
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 5 2022
Jun 22 2022
Nov 21 2021
Another option is to close stdin for the command feeding the pipe to grep (e.g., readelf):
Mar 5 2020
Nov 14 2019
I added a patch based on Joseph's patch here in the PR. It only addresses the EMACS circular dependency issue and doesn't include the update to 3.8. I attached the patch there instead of here to avoid confusion. Maybe there's a good way to present an alternate patchset on the phab page, but I don't know how.
May 18 2019
See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237972 to fix some cases of OPENSSL_LDFLAGS (with proposed fix for Uses/ssl.mk).
Dec 31 2018
Abandoning this change (probably not applicable to enough ports).
Sep 29 2018
Apr 16 2018
See recent comments in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227372 for stage-qa problems with this change.
Apr 8 2018
Jul 17 2017
May 4 2017
In D10554#219970, @mat wrote:And if all this is only to fix the couple of ports that extract their distfiles directly in STAGEDIR during install, I think those should be fixed instead, not the framework.
In D10554#219965, @mat wrote:This makes the shebangfix.mk code a lot more complicated.
In D10554#219966, @mat wrote:As a side note, if you need to "patch" shebangs after the build process has run, you are doing it wrong, you should provide the correct path, or patch the build process so that the correct shebangs are generated.
Added updates to three ports affected by the prospective changes to shebangfix.mk
Apr 30 2017
Apr 18 2017
Installing under ${PREFIX} (typically LOCALBASE) is generally preferred. The most common things installed outside of PREFIX/LOCALBASE are things under /var. Many kernel module ports install to /boot/modules.
Apr 14 2017
In D10398#215440, @cem wrote:Does that mean the port would need a runtime dependency on gdb for the /usr/local/share/gdb directory? If not, seems like a good idea to me.
I've seen other -gdb.py files installed to share/gdb/auto-load (such as /usr/local/share/gdb/auto-load/usr/local/lib/libglib-2.0.so.0.5000.2-gdb.py from the devel/glib20 port). Should the python -gdb.py file be installed there, too?
Dec 11 2016
What about packages that install libraries somewhere other than ${PREFIX}/lib? For example devel/llvmXY, installs to ${PREFIX}/llvmXY/lib and adds that path to a file in the ldconfig/ directory.
Nov 30 2016
I was trying to follow the discussion at llvm bug 30848, but the thread ran cold - there are still some unanswered investigation questions.
Nov 23 2015
That's ugly (my id which is my anti-spam email address). I wonder if phabricator has a setting to override that -- John Hein
Looks good. Thanks, Jan.