Re: [HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT
On 04/03/2019 23:16, Robert Huff wrote: > I was recently told the reason we need devel/llvm70 is the llvm > in base has - for reasons above my pay grade, but probably not above > yours - certain components disabled which are required by various > ports. The LLVM ports are still needed for those consumers that need their components, such as llvm-config and the like. Please refer to the aptly named wiki page again: https://wiki.freebsd.org/WhyDoIHaveToBuildLLVMWhenIAlreadyHaveClangInstalled > If 8.0 (in base) has those components enabled, then the odds are > good I can remove devel/llvm[67]0 - recovering almost 700 mb of disk > space and simplifying debugging efforts. > Major win for me; probably for others. > Think of it this way: the base system toolchain is *based on* some released version of LLVM (or GCC) as of a particular revision of base/. "Based on" means that components that are not critical to the actual functioning of the toolchain or otherwise useful to FreeBSD itself are bound to be stripped away when included and integrated in the base system. To illustrate this point, the first line of what `cc --version` prints on -CURRENT/amd64 r344788: FreeBSD clang version 8.0.0 (branches/release_80 355313) (based on LLVM 8.0.0) …whereas `clang80 --version` from devel/llvm80: clang version 8.0.0 (tags/RELEASE_800/rc2) So don't expect to even think about being able to opportunistically remove the LLVM ports, needed by consumers, on your system, anytime soon. -- Charlie Li …nope, still don't have an exit line. (This email address is for mailing list use; replace local-part with vishwin for off-list communication if possible) signature.asc Description: OpenPGP digital signature
Re: Missing timestamp implementation on rpi3
On Sun, Mar 03, 2019 at 03:46:39PM -0800, bob prohaska wrote: > On Sun, Mar 03, 2019 at 02:39:58PM -0700, Ian Lepore wrote: > > On Sun, 2019-03-03 at 10:54 -0800, bob prohaska wrote: > > > > > > The error it encountered is: > > > > > > No TimeStamp implementation on this platform. Build will not > > > succeed > > > > > > Correct the error condition and try again. > > > > > > See if this helps... > > > > https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201510=diff > > > > -- Ian > > The patch applied without complaint, but restarting make in www/firefox > promptly repeated the error. I'm trying make clean followed by make > in www/firefox presently. Does lang/rust and friends need rebuilding? > After cleaning www/firefox compiled and runs (slowly!). Rust seems to have rebuilt as part of the bycatch. Thank you! bob prohaska ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT
Jan Beich writes: > Robert Huff writes: > > > If this manages to truly replace previous versions a lot of people > > will want to know. > > What does "truly replace" mean? I was recently told the reason we need devel/llvm70 is the llvm in base has - for reasons above my pay grade, but probably not above yours - certain components disabled which are required by various ports. If 8.0 (in base) has those components enabled, then the odds are good I can remove devel/llvm[67]0 - recovering almost 700 mb of disk space and simplifying debugging efforts. Major win for me; probably for others. Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT
Robert Huff writes: > Jan Beich writes: > >> Recently /projects/clang800-import branch was merged[1] into /head. >> 13.0-CURRENT now comes with Clang/libc++/LLD 8.0.0 (RC3 atm) in >> base. Many ports have been fixed in advance but many also >> remain[2] broken. If you receive mail from pkg-fallout@ one of >> your port no longer builds on head-*-default jails or the package >> you're using is no longer available this maybe the cause. > > _Please_ make sure to announce this in src/UPDATING and > ports/UPDATING. src/UPDATING has 20190304: Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 8.0.0. Please see the 20141231 entry below for information about prerequisites and upgrading, if you are not already using clang 3.5.0 or higher. This mail is meant for non-current@ population of users that maybe confused as to what's going on. Clang upgrade in base doesn't affect just ports/ but all software not explicitly opting to use different compiler. As for ports/UPDATING default devel/llvm* update is a separate effort tracked in bug 235215. OTOH, it's not disruptive enough to warrant UPDATING entry due to few consumers. > If this manages to truly replace previous versions a lot of people > will want to know. What does "truly replace" mean? If you mean broken ports then no Clang upgrade ever had zero or, at least, none recently. Stuff gets fixed based on the number of ports blocked first and those people are interested in. Abandonware or ports without maintainers may never get fixed. This isn't really specific to Clang upgrades. A lot of ports end up being pruned each year due to failing to keep up with APIs of libraries they depend on. For one, Qt4 is going to be removed soon but a number of consumers haven't migrated to Qt5. GCC upgrades also frequently break consumers but the impact is smaller because it's not used on Tier1 architectures outside of Fortran as much. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT
Jan Beich writes: > Recently /projects/clang800-import branch was merged[1] into /head. > 13.0-CURRENT now comes with Clang/libc++/LLD 8.0.0 (RC3 atm) in > base. Many ports have been fixed in advance but many also > remain[2] broken. If you receive mail from pkg-fallout@ one of > your port no longer builds on head-*-default jails or the package > you're using is no longer available this maybe the cause. _Please_ make sure to announce this in src/UPDATING and ports/UPDATING. If this manages to truly replace previous versions a lot of people will want to know. Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT
Recently /projects/clang800-import branch was merged[1] into /head. 13.0-CURRENT now comes with Clang/libc++/LLD 8.0.0 (RC3 atm) in base. Many ports have been fixed in advance but many also remain[2] broken. If you receive mail from pkg-fallout@ one of your port no longer builds on head-*-default jails or the package you're using is no longer available this maybe the cause. [1] https://svnweb.freebsd.org/changeset/base/344779 [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236062 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
devel/valgrind not working
Hello. I've been using valgrind for a long time. After some months without using it, today it does not work anymore. # freebsd-version -ku 11.2-RELEASE-p9 11.2-RELEASE-p8 # uname -p amd64 # pkg info | grep valgrind valgrind-3.10.1.20160113_7,1 Memory debugging and profiling tool # valgrind --version valgrind-3.10.1 # valgrind ls ==15396== Memcheck, a memory error detector ==15396== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==15396== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==15396== Command: ls ==15396== Bad system call (core dumped) Reading the core doesn't give any useful info. Same goes for devel/valgrind-devel. Any hint? bye & Thanks av. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [devel/arduino18] Adding a new board description.
On Mon, Mar 4, 2019 at 4:37 AM Peter Jeremy wrote: > > I'm trying to use devel/arduino18 with a non-standard board - which > requires installing a new board description. According to the board > documentation, the process is to enter the URL for the new board > description in the Preferences, then go to Tools -> Board -> Boards > Manager to actually install the definitions. My difficulty is that > the above option doesn't exist because the patches included with ports > r438914 delete all the relevant code. > > I haven't found any discussion as to why the boards manager was removed > or what the alternatives are for installing new board descriptions. > > Can anyone advise the process for adding new board descriptions? > (a CC is appreciated; most posts to this list get filtered locally otherwise...) I'll find some time this week to see what I can do to bring the board manager back. It was removed when I initially ported Arduino 1.6.x because there was some conflict in the functionality itself with how we patch other bits, but I'm foggy on the details at this point because that's been a couple years. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/ocaml-extlib | 1.7.5 | 1.7.6 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[devel/arduino18] Adding a new board description.
I'm trying to use devel/arduino18 with a non-standard board - which requires installing a new board description. According to the board documentation, the process is to enter the URL for the new board description in the Preferences, then go to Tools -> Board -> Boards Manager to actually install the definitions. My difficulty is that the above option doesn't exist because the patches included with ports r438914 delete all the relevant code. I haven't found any discussion as to why the boards manager was removed or what the alternatives are for installing new board descriptions. Can anyone advise the process for adding new board descriptions? -- Peter Jeremy signature.asc Description: PGP signature
