From nobody Fri May 27 22:21:24 2022 X-Original-To: freebsd-riscv@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 AD15A1B4BDF0 for ; Fri, 27 May 2022 22:21:33 +0000 (UTC) (envelope-from jrtc27@jrtc27.com) Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4L8zmX70cTz3pLr for ; Fri, 27 May 2022 22:21:32 +0000 (UTC) (envelope-from jrtc27@jrtc27.com) Received: by mail-wr1-f41.google.com with SMTP id k16so3217079wrg.7 for ; Fri, 27 May 2022 15:21:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mIEv+F++YbJEQ+OOLRmS9KRDSM37VnQDdk9ccHac6/g=; b=ezviNFrT/2dxlQ53RtVvqfosKUen4gD6tmwMuN+yxIQXFaqFf+HqSMz3tFwFwAeZKD Sj2R0cAPqzA88EH9Yr31plUTY8SQg7J6Djk90jUm/XeemG4a9yn8V34xzRhUJ2HH/Epw obgRuouLppKWWMFMBSPFUcVA+MUiWdcFwyPX3p9KDMSEopBsZowtA0KlMRJ3LNeq8XwB POA3RpJe8ywkKRZwkthyQwtLxaTtA0CBDkY0JXWLAGRIxyoAZm0EiMz797f5VbbVTMRL 81Xh20GTImbF0PAgfopDiUNLeCpkhoeUR5WlsxWiArnXOeiew5SibYTtfxlLZrht7ktL WzTA== X-Gm-Message-State: AOAM533oDMbltuYRi0ui24gGM9tyw57aEsPjNm1cmwhYuiN1gW06dH1p rI4TbFx/7RZ4CjWHr2OPeAGYP8nKf2qQ0g== X-Google-Smtp-Source: ABdhPJwbzUPSiUDwox1BqYt8BvLw4kUuPP5iRuZ/x9eb4E+rhx/qHyM42P0rGqcr9Ex6GhoqwRaWhg== X-Received: by 2002:a05:6000:14f:b0:210:1d70:d5e0 with SMTP id r15-20020a056000014f00b002101d70d5e0mr3451599wrx.359.1653690086054; Fri, 27 May 2022 15:21:26 -0700 (PDT) Received: from smtpclient.apple (global-5-141.nat-2.net.cam.ac.uk. [131.111.5.141]) by smtp.gmail.com with ESMTPSA id n11-20020a5d598b000000b0020ce1c1cf31sm2809078wri.21.2022.05.27.15.21.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 May 2022 15:21:25 -0700 (PDT) Content-Type: text/plain; charset=utf-8 List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-riscv@freebsd.org X-BeenThere: freebsd-riscv@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\)) Subject: Re: Is there no working clang in FreeBSD/RISC-V's ports? From: Jessica Clarke In-Reply-To: <2AE7AF78-729F-4D6B-AF62-9A79703343D8@hamburg.de> Date: Fri, 27 May 2022 23:21:24 +0100 Cc: "freebsd-riscv@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <2AE7AF78-729F-4D6B-AF62-9A79703343D8@hamburg.de> To: "lars.sonchocky-helldorf@hamburg.de" X-Mailer: Apple Mail (2.3696.80.82.1.1) X-Rspamd-Queue-Id: 4L8zmX70cTz3pLr X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of jrtc27@jrtc27.com designates 209.85.221.41 as permitted sender) smtp.mailfrom=jrtc27@jrtc27.com X-Spamd-Result: default: False [-1.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[jrtc27@freebsd.org,jrtc27@jrtc27.com]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[jrtc27@freebsd.org,jrtc27@jrtc27.com]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[jrtc27]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-riscv@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.221.41:from]; TO_DN_EQ_ADDR_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-riscv]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.221.41:from]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 27 May 2022, at 22:41, lars.sonchocky-helldorf@hamburg.de wrote: >=20 > Hi everybody, >=20 >=20 > meanwhile I=E2=80=99ve found out that there is no longer a clang-port = available, it got merged back into the llvm-devel port: >=20 > https://www.freshports.org/devel/llvm-devel/ (See port moves) >=20 >=20 > So I changed GNUstep=E2=80=99s install-dependencies-freebsd script to = require the llvm-devel port. You don=E2=80=99t want that; llvm-devel is snapshots of LLVM=E2=80=99s = development branch. You want just llvm, which is the latest officially released version, if you need a package at all, which I doubt is actually the case (see below). > This worked fine on FreeBSD/amd64 inside Virtual Box but not for = FreeBSD/RISC-V in QEMU: >=20 > pkg: No packages available to install matching 'llvm-devel' have been = found in the repositories >=20 >=20 > So is there really no llvm-devel port available for FreeBSD/RISC-V? Indeed, depending on what repo you want, there is currently no version of that built, nor recent released versions of LLVM, due to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261374. The bug has been fixed but as far as I can tell no recent rebuild has happened for the 14 latest repo, only the 13 quarterly repo. > Another thing that caught my attention is, that freshports.org never = seems to mention any RISC-V availability. I thought that with FreeBSD 13 = the RISC-V architecture moved to Tier-2 support ( = https://wiki.freebsd.org/riscv#Current_Status ). Doesn=E2=80=99t that = mean that there should be such ports available for RISC-V?=20 That=E2=80=99s just a freshports data gathering issue, it doesn=E2=80=99t = know the riscv64 package sets exist so doesn=E2=80=99t report on them. I=E2=80=99ve= filed https://github.com/FreshPorts/freshports/issues/364 for this. > Quote from = https://docs.freebsd.org/en/articles/committers-guide/#archs >=20 > =E2=80=A2 Tier 2 platforms should be self-hosting either via the = in-tree toolchain or an external toolchain. If an external toolchain is = required, official binary packages for an external toolchain will be = provided. >=20 > doesn=E2=80=99t specifically that mean that the llvm-devel port should = be available? Just asking =E2=80=A6 RISC-V is self-hosting via the in-tree toolchain, thus no external toolchain is required, and thus no official binary packages are required to be provided. Out of the box you can compile with Clang and link with LLD, no packages needed. You only need the packages if you need a different specific version or you need to use = libLLVM/libClang=E2=80=99s APIs. Jess > Kind regards, >=20 > Lars >=20 >=20 >> Am 22.05.2022 um 23:18 schrieb lars.sonchocky-helldorf@hamburg.de: >>=20 >> Hi there, >>=20 >>=20 >> the GNUstep project (but in reality just me myself and I) has = undergoing efforts of porting GNUstep to the RISC-V platform. While this = was mainly a no-brainer for Linux-Fedora/RISC-V (some minor tweaks were = necessary), it seems on the FreeBSD side are some more serious efforts = necessary. I think this will not be my last E-Mail in this regard to the = list. Hope you can stand this! >>=20 >> Firstly I was going to install all the necessary dependencies of = GNUstep for RISC-V. I used their http://github.com/gnustep/tools-scripts = : >>=20 >> $ sudo ./tools-scripts/install-dependencies-freebsd >>=20 >> which resulted in installing most of all the dependencies but: >>=20 >>=20 >> pkg: No packages available to install matching 'libobjc2' have been = found in the repositories >>=20 >> this is our (GNUstep=E2=80=99s) responsibility=20 >>=20 >>=20 >> pkg: No packages available to install matching 'clang' have been = found in the repositories >>=20 >> no idea how to fix this. Is there really no RISC-V hosted clang = available? >>=20 >>=20 >> pkg: No packages available to install matching 'libxml' have been = found in the repositories >> pkg: No packages available to install matching 'avahi' have been = found in the repositories >>=20 >> no idea who is in charge here to make those work, I am willing to = test certain things if guided. >>=20 >>=20 >> Kind regards, >>=20 >> Lars >>=20