[cfe-dev] FreeBSD + clang36 + groff dependency

[Sergey.Praskovin.GDC@ts.fujitsu.com via cfe-dev]

Hello Guys.
Maybe someone could help me with the issue? Talked to Brooks Davis from FreeBSD.org but he can't help here, PSB.
Clang has a groff as a dependency is there a wads to get rid of it. (I use mdocml as a replacement)

Kind regards
Sergey Praskovin





-----Original Message-----
From: Brooks Davis [mailto:brooks at freebsd.org] 
Sent: Friday, January 22, 2016 10:05 PM
To: Praskovin, Sergey (GDC)
Cc: brooks at FreeBSD.org
Subject: Re: FreeBSD + clang36 + groff dependency

On Fri, Jan 22, 2016 at 08:05:26AM +0000, Sergey.Praskovin.GDC at ts.fujitsu.com wrote:
> Hello Brooks!
> I got a small question for you regarding building of clang36.
> I've replaced groff from base with mdocml, but when Clang is being built from ports it exits with error not being able to find the groff:
> 
> groff -Tps -man 
> /usr/obj/usr/ports/lang/clang36/work/llvm-3.6.2.src/tools/clang/docs/t
> ools/clang.1 > 
> /usr/obj/usr/ports/lang/clang36/work/llvm-3.6.2.src/tools/clang/docs/t
> ools/clang.ps
> groff: not found
> Makefile:76: recipe for target 
> '/usr/obj/usr/ports/lang/clang36/work/llvm-3.6.2.src/tools/clang/docs/
> tools/clang.ps' failed
> gmake[2]: *** 
> [/usr/obj/usr/ports/lang/clang36/work/llvm-3.6.2.src/tools/clang/docs/
> tools/clang.ps] Error 127 rm 
> /usr/obj/usr/ports/lang/clang36/work/llvm-3.6.2.src/tools/clang/docs/t
> ools//.dir
> gmake[2]: Leaving directory '/usr/obj/usr/ports/lang/clang36/work/llvm-3.6.2.src/tools/clang/docs/tools'
> *** Error code 2
> 
> Stop.
> make[1]: stopped in /usr/ports/lang/clang36
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/lang/clang36
> 
> 
> Is there a way to get rid of groff completely?

I'd guess that if you installed textproc/groff it would work in this port.  I suppose a BUILD_DEPEND could be added or the source could be patched to support mdocml here, but I don't really consider this to be a supported configuration.  If it is supposed to be a supported configuration then there should be a policy that it is supported and a USES=groff:build should exist.

-- Brooks