Date: Mon, 20 Aug 2018 22:37:48 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 230767] [NEW PORT] graphics/libheif: an ISO/IEC 23008-12:2017 HEIF file format decoder and encoder Message-ID: <bug-230767-7788-MEMxo4zhxe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230767-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-230767-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230767 --- Comment #4 from Sebastian Steinmetz <freebsd-2018@sebastiansteinmetz.ch= > --- Hi Kurt, thanks for reviewing this so quickly. I don't have an idea what the problem would be with the free identifier in encoder_fuzzer.cc. I always though free() would be a normal C keyword to fr= ee some memory. Didn't know it could cause the compiler to issue any errors... But I see some commits agains master branch in the repository which are not= yet tagged as a release. Maybe we could try to make a build from the most recent development branch and report compiler issues upstream? I can't reproduce the prob on my end, the port builds just fine for my Free= BSD 11.1 jail in freenas. Not even complaining about any missing USES=3Dpkgconf= ig. But I guess it doesn't hurt to add it. Same goes for the BROKEN_FreeBSD_10 setting. Find attached another patch with the respective changes. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230767-7788-MEMxo4zhxe>