Re: [HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT

2019-03-04 Thread Charlie Li via freebsd-ports
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

Re: Missing timestamp implementation on rpi3

2019-03-04 Thread bob prohaska
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

Re: [HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT

2019-03-04 Thread Robert Huff
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

Re: [HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT

2019-03-04 Thread Jan Beich
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/UPDATIN

[HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT

2019-03-04 Thread Robert Huff
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

[HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT

2019-03-04 Thread Jan Beich
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

devel/valgrind not working

2019-03-04 Thread Andrea Venturoli
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

Re: [devel/arduino18] Adding a new board description.

2019-03-04 Thread Kyle Evans
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,

FreeBSD ports you maintain which are out of date

2019-03-04 Thread portscout
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,

[devel/arduino18] Adding a new board description.

2019-03-04 Thread Peter Jeremy
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