From nobody Fri Feb 10 01:07:39 2023 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PCbF82Vn4z3pm8W for ; Fri, 10 Feb 2023 01:07:40 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PCbF80VQlz3nBY for ; Fri, 10 Feb 2023 01:07:40 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Authentication-Results: mx1.freebsd.org; none Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 0D07B3C0199; Fri, 10 Feb 2023 01:07:39 +0000 (UTC) Date: Fri, 10 Feb 2023 01:07:39 +0000 From: Brooks Davis To: Steve Kargl Cc: freebsd-ports@freebsd.org Subject: Re: devel/llvm16 -- flang is still broken Message-ID: References: List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: X-Rspamd-Queue-Id: 4PCbF80VQlz3nBY X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:199.48.128.0/22, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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