Re: [HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT
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 thing I thinking about. > 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. That may be the path of wisdom; and I understand keeping things working is a non-trivial job, for which I thank those who do it. Please understand my ... frustration ... in having to deal with the conseqences, particularly with regard to the ongoing drm changes. To return to my original point, this is why I suggested an entry in ports/UPDATING - to let others in my position know of possible impact. 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: devel/valgrind not working
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
compiled for both on machine "B").
As a test, I also installed valgrind with portupgrade on machine "B"
(the one that runs Poudriere): the text I pasted comes from this setup
(so for sure same kernel, as valgrind was just freshly compiled).
I'll try rebuilding and reinstalling world (even if it should not really
change, apart from version number); if something different happens I'll
report back.
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 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 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. > > I had a go at re-enabling the board manager and ran into a problem with > package_index.json. The port installs native versions of all the IDE > dependencies, creates links from /usr/local/arduino/tools-builder to the > native versions and hand-crafts a package_index_bundled.json that says the > tool runs on the appropriate FreeBSD version (amd64-freebsd12 in my case). > If I start the board manages, the IDE downloads fresh copy of package data > and installs it as ~/.arduino15/package_index.json - this version is > unpatched and therefore only lists the "supported" tool versions (Linux, > MacOS & Windows), leading to a null pointer exception. > Right, I'm starting to remember the details now... they want to package all of these things up for the platforms they officially support, but we're not a supported platform so the system absolutely freaks out and it was a very large rabbit hole (at the time) to go down for making any of this work. I haven't started the support conversation yet upstream -- by the time I got all of my other work upstreamed, I ran out of time to pursue that. I had asked if I can add some concept of 'unsupported platforms' to the IDE to bypass a lot of the checks that they do, but I had received no response and ran out of time to follow-up. > Interestingly, the release notes for 1.8.2 include: > * Allow BoardManager to fetch FreeBSD tools (thanks @kevans91) > so it seems you have previously fixed the board manager, but the fix > no longer works. > This was my start at getting to where we need to be to stop patching out this functionality, but it turns out there's a lot more hurdles to talk about. The path forward for you is unfortunately going to be hacking it out locally, or we can look at patching it into the arduino-core port. The level of effort kind of depends on whether it's AVR/SAM/SAMD core or another core that we don't currently package -- needs range from patching the core's boards.txt to porting a new core (relatively easily also). ___ 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/valgrind not working
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 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/valgrind not working
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 | 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? 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? # freebsd-version -ku 11.2-RELEASE-p9 11.2-RELEASE-p9 > > 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" -- /* * Serpent7776 */ ___ 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"
