Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Mar 2019 09:44:27 +0100
From:      Andrea Venturoli <ml@netfence.it>
To:        Kurt Jaeger <pi@opsec.eu>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: devel/valgrind not working [SOLVED]
Message-ID:  <7573230c-3a06-e586-98a5-18ebb704e38c@netfence.it>
In-Reply-To: <143665c5-cbb3-57a3-081d-1a48568b8dd3@netfence.it>
References:  <ea61170d-f5d5-ad7b-c488-7f067b387cbd@netfence.it> <20190305164343.109d3986@DaemONX> <e0a5fa31-1e44-3051-32e6-c20363bf2c60@netfence.it> <20190305160643.GB47280@home.opsec.eu> <143665c5-cbb3-57a3-081d-1a48568b8dd3@netfence.it>

next in thread | previous in thread | raw e-mail | index | archive | help
On 3/5/19 5:26 PM, Andrea Venturoli wrote:

> 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.

As expected, upgrading world from 11.2p8 to 11.2p9 did not change anything.

I had a suggestion off-list which solved: valgrind needs 
COMPAT_FREEBSD10 in the kernel configuration.
I thought I didn't need this and had removed it.

Altough this options comes in GENERIC, I'd suggest mentioning it in pkg 
message.

  bye & Thanks
	av.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7573230c-3a06-e586-98a5-18ebb704e38c>