Charlie Li writes:
> 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
This was the th
On 3/5/19 5:06 PM, Kurt Jaeger wrote:
Which begs the question: for which kernel was valgrind compiled ?
I had the original problem in a jail on machine "A"; valgrind was
compiled on an identical machine ("B") with Poudriere.
Machine "A" and "B" run the same kernel and userland (the latter
co
On Tue, Mar 5, 2019 at 4:49 AM Peter Jeremy wrote:
>
> On 2019-Mar-04 08:36:52 -0600, Kyle Evans wrote:
> >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 function
On 3/5/19 4:43 PM, Serpent7776 wrote:
Working fine for me with same setup with exception of patch level which is both
-p9. Maybe your userland is out of sync with the kernel?
AFAICT there is no difference in userland between p8 and p9.
p8 to p9 modification only affects kernel.
bye & Thanks
On Mon, 4 Mar 2019 17:27:45 +0100
Andrea Venturoli wrote:
> 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 | gr
On 2019-Mar-04 08:36:52 -0600, Kyle Evans wrote:
>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 t
