Date: Fri, 10 Feb 2023 01:07:39 +0000 From: Brooks Davis <brooks@freebsd.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-ports@freebsd.org Subject: Re: devel/llvm16 -- flang is still broken Message-ID: <Y%2BWY26rQbE1BEqQR@spindle.one-eyed-alien.net> In-Reply-To: <Y%2BWXAc%2ByDj9Js1oW@troutmask.apl.washington.edu> References: <Y%2BVuj8AUo47vMHtv@troutmask.apl.washington.edu> <Y%2BWXAc%2ByDj9Js1oW@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 09, 2023 at 04:59:45PM -0800, Steve Kargl wrote:
> On Thu, Feb 09, 2023 at 02:07:11PM -0800, Steve Kargl wrote:
> > TL:DR: Please disable building flang in devel/llvm16.
> >=20
> >=20
> > I was hoping to test the to Fortran compilers included in
> > devel/llvm16. Unfortunately, neither flang16 nor flang-new16
> > are usable.
> >=20
>=20
> This seems to work for a simple program. Have no idea if
> the order of libs is correct.
>=20
> --- flang16.orig 2023-02-09 16:57:35.384452000 -0800
> +++ flang16 2023-02-09 16:57:57.163685000 -0800
> @@ -7,5 +7,9 @@
> [ -L "$tool" ] && tool=3D$(/bin/realpath $tool)
> tool=3D${tool##*/}
> tool=3D"${LLVM_PREFIX}/bin/${tool%${LLVM_SUFFIX}}"
> -LD_LIBRARY_PATH=3D"${LD_LIBRARY_PATH:+${LD_LIBRARY_PATH}:}${LLVM_PREFIX}=
/lib" \
> - exec "${tool}" "${@}"
> +#LD_LIBRARY_PATH=3D"${LD_LIBRARY_PATH:+${LD_LIBRARY_PATH}:}${LLVM_PREFIX=
}/lib" \
> +# exec "${tool}" "${@}"
> +exec "${tool}" "${@}" -L${LLVM_PREFIX}/lib \
> +-lFortranCommon -lFortranDecimal -lFortranEvaluate \
> +-lFortranLower -lFortranParser -lFortranSemantics \
> +-lFortran_main -lFortranRuntime -lm
I'm somewhat minded to either turn it off by default or apply
https://reviews.llvm.org/D143592 locally. There's a contingent that
seems to think flang must be essentially perfect before they make it at
all usable and that seems a backwards to me.
-- Brooks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Y%2BWY26rQbE1BEqQR>