Call for 2017Q4 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is January 14, 2018, for work done in October through December. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about work that is underway and completed. Submission of reports is not restricted to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred and easiest submission method is to use the XML generator [1] with the results emailed to the status report team at mont...@freebsd.org . (Do be sure, though, to save the form output and not the form itself! In particular, the Google Chrome "save as" function does not save the generated output for some reason.) There is also an XML template [2] that can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [3]. You can also review previous issues [4][5] for ideas on the style and format. We look forward to seeing your 2017Q4 reports! Thanks, Ben (on behalf of monthly@) [1] https://www.FreeBSD.org/cgi/monthly.cgi [2] https://www.FreeBSD.org/news/status/report-sample.xml [3] https://www.FreeBSD.org/news/status/howto.html [4] https://www.FreeBSD.org/news/status/report-2017-07-2017-09.html [5] https://www.FreeBSD.org/news/status/report-2017-04-2017-06.html signature.asc Description: PGP signature
FreeBSD Quarterly Status Report - Third Quarter 2017
FreeBSD Project Quarterly Status Report - 3rd Quarter 2017 This quarter's FreeBSD developments continue to provide excitement and promise for further developments. I myself have a soft spot for manual pages, so it is especially good to see that we have gained some documentation for writing them (and I hope that this will translate to more and improved manual pages in the future!). The core@ entry is also of particular note, with the introduction of the FCP process and the recognition of the first non-committer FreeBSD Project Member (and more). Read on to find out more about these, as well as improved support for the AMD Zen family of processors (e.g., Ryzen), and a whole lot more! --Benjamin Kaduk __ The deadline for submissions covering the period from October to December 2017 is January 14, 2017. __ FreeBSD Team Reports * FreeBSD Release Engineering Team * Ports Collection * The FreeBSD Core Team * The FreeBSD Foundation Projects * FreeBSD CI Kernel * Intel 10G iflib Driver Update * Intel iWARP Support * pNFS Server Plan B Architectures * AMD Zen (family 17h) support Userland Programs * Updates to GDB Ports * FreeBSDDesktop * OpenJFX 8 * Puppet Documentation * Absolute FreeBSD, 3rd Edition * Manual Pages Third-Party Projects * The nosh Project __ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Release Engineering Team Links FreeBSD 11.1-RELEASE Announcement URL: https://www.FreeBSD.org/releases/11.1R/announce.html FreeBSD 10.4-RELEASE Schedule URL: https://www.FreeBSD.org/releases/10.4R/schedule.html FreeBSD Development Snapshots URL: https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/ Contact: FreeBSD Release Engineering Team The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes, and maintaining the respective branches, among other things. The FreeBSD Release Engineering Team continued finalizing the 11.1-RELEASE cycle, with the final release builds starting on July 21 and the official release announcement email sent on July 26. Thank you to everyone who helped test 11.1-RELEASE, ensuring its quality and stability. [1] FreeBSD 11.1-RELEASE is the second release from the stable/11 branch. Additionally, the FreeBSD Release Engineering Team started the 10.4-RELEASE cycle, with the code slush starting on July 28. With the final release build expected to start on September 29 and the official announcement overlapping the end of the quarter, everything is on schedule as of this writing. [2] FreeBSD 10.4-RELEASE will be the fifth release from the stable/10 branch, and is planned to be the final release of the 10.x series. This project was sponsored by The FreeBSD Foundation [1]. This project was sponsored in part by The FreeBSD Foundation [2]. __ Ports Collection Links About FreeBSD Ports URL: https://www.FreeBSD.org/ports/ Contributing to Ports URL: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html FreeBSD Ports Monitoring URL: http://portsmon.freebsd.org/index.html Ports Management Team Website URL: https://www.freebsd.org/portmgr/index.html FreeBSD portmgr on Twitter (@freebsd_portmgr) URL: https://twitter.com/freebsd_portmgr/ FreeBSD Ports Management Team on Facebook URL: https://www.facebook.com/portmgr FreeBSD Ports Management Team on Google+ URL: https://plus.google.com/communities/108335846196454338383 Contact: René Ladan Contact: FreeBSD Ports Management Team The Ports Collection now features over 31,600 ports. There are currently 2671 problem reports, of which 718 are unassigned. This quarter saw almost 5,900 commits from 175 committers. The number of open PRs grew compared to last quarter, and outpaced the number of changes. This quarter, we welcomed Zach Leslie (zleslie@), Luca Pizzamiglio (pizzamig@), Craig Leres (leres@), Adriaan de Groot (adridg@), and Dave Cottlehuber (dch@) as new committers. The commit bits of the following committers were taken in for safekeeping: alonso@ after 19 months of inactivity, rpaulo@ per his request, and ache@ after he passed away. Despite several tries and changing mentors, kami@ lacked interest in completing his mentorship, so his commit bit was also taken in for safekeeping. On the infrastructure side, two USES values were
Re: LLD: man pages missing?
On Mon, Dec 25, 2017 at 09:16:24PM +0100, O. Hartmann wrote: > > Can someone help? > There isn't a lld.1 manpage. grep MAN /usr/src/usr.bin/clang/lld/Makefile MAN= google 'man lld' eventually get one to https://lld.llvm.org/#using-lld which leads one to assume that there is no documentation for lld. -- Steve ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: LLD: man pages missing?
On Monday, December 25, 2017, Dimitry Andric wrote: > On 25 Dec 2017, at 21:16, O. Hartmann wrote: > > > > I have installed most recent CURRENT as of r327219 with LLD_IS_LD=YES set > > via /etc/src.conf. > > > > I try to find some options and tried "man ld", "man lld" and "ld.lld". > In the the latter > > two cases there can nothing be found on the system and man ld always > seems to refer to > > the GNU linker - which is, I believe, the linker reached by > /usr/bin/ld.bfd. There is > > also a linker "ld" in /usr/local/bin/ld from binutils-2.28,1. > > There is no manpage yet. Upstream provides a bit of Sphinx-based > documentation (e.g. in .rst format), but there is no specific manpage. > > Since lld is now approaching a quite usable state, maybe it is time for > a request to upstream to provide one. ;) The same would be nice for clang too. Its default man page is poor. > > -Dimitry > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: LLD: man pages missing?
On 25 Dec 2017, at 21:16, O. Hartmann wrote: > > I have installed most recent CURRENT as of r327219 with LLD_IS_LD=YES set > via /etc/src.conf. > > I try to find some options and tried "man ld", "man lld" and "ld.lld". In the > the latter > two cases there can nothing be found on the system and man ld always seems to > refer to > the GNU linker - which is, I believe, the linker reached by /usr/bin/ld.bfd. > There is > also a linker "ld" in /usr/local/bin/ld from binutils-2.28,1. There is no manpage yet. Upstream provides a bit of Sphinx-based documentation (e.g. in .rst format), but there is no specific manpage. Since lld is now approaching a quite usable state, maybe it is time for a request to upstream to provide one. ;) -Dimitry signature.asc Description: Message signed with OpenPGP
LLD: man pages missing?
I have installed most recent CURRENT as of r327219 with LLD_IS_LD=YES set via /etc/src.conf. I try to find some options and tried "man ld", "man lld" and "ld.lld". In the the latter two cases there can nothing be found on the system and man ld always seems to refer to the GNU linker - which is, I believe, the linker reached by /usr/bin/ld.bfd. There is also a linker "ld" in /usr/local/bin/ld from binutils-2.28,1. Can someone help? Thnaks, oh -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). pgpr3KQjlJSuQ.pgp Description: OpenPGP digital signature
Re: Unable to build 12-current/amd64
On 2017-Dec-23 13:42:40 +0100, Dimitry Andric wrote: >On 23 Dec 2017, at 10:56, Peter Jeremy wrote: >> >> Since r326496, buildworld on my 12-current/amd64 system has consistently >> died as follows. >... >> /usr/src/contrib/llvm/tools/clang/lib/Basic/SourceManager.cpp:1166:10: fatal >> error: 'emmintrin.h' file not found >> #include >> ^ >> 1 error generated. >> *** Error code 1 >> >> Stop. >> make[4]: stopped in /usr/src/lib/clang/libclang >> >> I'm building on a 12.0-CURRENT VirtualBox guest at r326430. I've checked >> that my /usr/src is clean and deleted /usr/obj to no effect. I have dug >> into SourceManager.cpp and the #include is protected by a #if __SSE2__, >> which is relying on clang internal checks to define (and my CPU supports >> SSE2). Does anyone have any ideas to explain what is going on? > >First of all, does your host system have emmintrin.h? E.g. what is the >output of "find /usr/lib/clang -name emmintrin.h" ? Aha. Somehow my entire /usr/lib/clang/5.0.0 tree was missing. I'm not sure if that was an installworld glitch or something I accidently did. In any case, restoring it has fixed the problem. Thanks for the pointer. -- Peter Jeremy signature.asc Description: PGP signature
BUG: LLVM: : CommandLine Error: Option 'enable-value-profiling' registered more than once!
I'm not a compiler expert and I have some serious trouble getting port lang/pocl to work properly. I'm on CURRENT (FreeBSD 12.0-CURRENT #79 r327170: Mon Dec 25 03:35:27 CET 2017 amd64). The problem persits on both LLD_IS_LD set or not. Whenever lang/pocl in combination with devel/ocl-icd is installed and more than one OpenCL ICD is installed with lang/pocl, any client (compiled with lang/pocl) or port/package utilising OpenCL in any way (see graphics/blender PR23879 or devel/clinfo, bails out with: : CommandLine Error: Option 'enable-value-profiling' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options Looking at the POCL repo at github gives noch much help about this, they closed an error report stating it isn't POCL related, but a long-standig LLVM issue, please see https://github.com/pocl/pocl/issues/474. Searching the net for this sepcific error reveals this bug at llvm.org's bug report: [...] Don't link ObjCARCOpts twice. Fixes PR22543 https://reviews.llvm.org/rL240104 Taken that information, the "bug" is considered solved - but it is lldb related, not lld or whatever is causing the error for POCL! I also found this one, still open: [...] Bug 22952 - cl::opt + LLVM_BUILD_LLVM_DYLIB is completely broken https://bugs.llvm.org/show_bug.cgi?id=22952 I do not have the experience, brains and resources to look into this matter any deeper, so I'd appreciate someone with insight into LLVM could take a look at this. When I look what OpenCL ICDs are installed apart from lang/pocl on my boxes, I see this installation: 5618138 -rw-r--r-- 1 root wheel - 33B Dec 25 03:35 intel-beignet.icd 5618040 -rw-r--r-- 1 root wheel - 19B Dec 17 15:48 mesa.icd [5617930 -rw-r--r-- 1 root wheel - 31B Dec 23 11:21 pocl.icd] Testing with port devel/clinfo and with(!) lang/pocl installed, gives the error I stated initially. Deleting lang/pocl, devel/clinfo dies any way with this error: [...] Unable to find symbol pthread_mutexattr_setkind_np version (null). Aborting. Abort or it simply hangs [Ctrl-T]: load: 0.12 cmd: clinfo 82286 [uwait] 46.78r 0.02u 0.00s 0% 50964k Something isn't right here. A far more serious port is graphics/blender. With usage of OpenCL and having lang/pocl installed, I receive the error initially mentioned. I've provided a DIFF to to the (marked broken) lang/pocl version 0.14 (for this sepcific PR see Bug 223032 - [PATCH] lang/pocl: pkg-static fails due to wrong pkg-plist entries, look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223032): POCL 1.0: Bug 224584 - [PATCH] lang/pocl: fix pkg-plist and update to POCL 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224584 Hopefully,someone has the time to have a look into this. Kind regards, Oliver -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). pgpLnRELpraC3.pgp Description: OpenPGP digital signature
