20190524 trunk - where is clang compiler

[libRh]

Anyone know where the clang compiler is? Fist time using pkgsrc on macOS HighSierra. I want to install the latest clang version.

[krytarowski]

lang/clang ?

[libRh]

sudo pkgin -y install clang
clang is not available in the repository
calculating dependencies...done.

[krytarowski]

What's the repo? For macos I recommend to prompt joyent @jperkin .

[libRh]

that wahts I've done

Copy and paste the lines below to install the 64-bit Sierra set.

These packages are suitable for anyone running Sierra (10.12.6) or newer,

and are updated from pkgsrc trunk every few days.

BOOTSTRAP_TAR="bootstrap-trunk-x86_64-20190524.tar.gz"
BOOTSTRAP_SHA="1c554a806fb41dcc382ef33e64841ace13988479"

Download the bootstrap kit to the current directory.

curl -O https://pkgsrc.joyent.com/packages/Darwin/bootstrap/${BOOTSTRAP_TAR}

Verify the SHA1 checksum.

echo "${BOOTSTRAP_SHA} ${BOOTSTRAP_TAR}" >check-shasum
shasum -c check-shasum

Verify PGP signature. This step is optional, and requires gpg.

curl -O https://pkgsrc.joyent.com/packages/Darwin/bootstrap/${BOOTSTRAP_TAR}.asc
curl -sS https://pkgsrc.joyent.com/pgp/1F32A9AD.asc | gpg --import
gpg --verify ${BOOTSTRAP_TAR}{.asc,}

Install bootstrap kit to /opt/pkg

sudo tar -zxpf ${BOOTSTRAP_TAR} -C /

Reload PATH/MANPATH (pkgsrc installs /etc/paths.d/10-pkgsrc for new sessions)

eval $(/usr/libexec/path_helper)

I completely new to this I try to learn C

[bsiegert]

Looking at the latest package build results ( https://bulktracker.appspot.com/pkg/ag1zfmJ1bGt0cmFja2VyciILEgVidWlsZBiAgICQvZGdCQwLEgNwa2cYgICAvNv2_QkM), I see that clang is indirect-failed because LLVM failed to build. Here is the LLVM build log: http://us-east.manta.joyent.com/pkgsrc/public/reports/Darwin/trunk/x86_64/20190128.1951//llvm-7.0.1/build.log

[libRh]

Oh okay so no clang for me? Will it eventually get fixed anytime soon?

[spchamp]

The CC, CXX, and LD used for the build may, in ways, affect the build process. Albeit not on a BSD, I've been able to build a full LLVM toolchain on Debian 8 and more recently, on Debian 10, using the host LLVM toolchain distro – respectively, Debian LLVM 4 and LLVM 7 distributions.

imoe; LLVM 8 from pkrsrc seems to work out for for building in pkgsrc, locally, once the initial pkgsrc LLVM build+install completes, using the host's LLVM distro – also using libcxx, libcxxabi (building on a Linux) and lld initially from the host OS distro, to build all those via pkgsrc. imoe it works out after the stage-1 build, using the host toolchain distro, namely LLVM. in that first build.

imoe it also works out on FreeBSD 11.2 … under some local config.

May there be another CC, CXX and LD available on the host, for the LLVM build?

[Midar]

Given how old this is, can this be closed?

[sskras]

@Midar commented on Jan 3, 2021:

Given how old this is, can this be closed?

It unclear from the responses from author. Ping @libXq

[sskras]

@libXq commented on Jul 19, 2019:

Anyone know where the clang compiler is? Fist time using pkgsrc on macOS HighSierra. I want to install the latest clang version.

@bsiegert commented on Jul 19, 2019:

Looking at the latest package build results ( https://bulktracker.appspot.com/pkg/ag1zfmJ1bGt0cmFja2VyciILEgVidWlsZBiAgICQvZGdCQwLEgNwa2cYgICAvNv2_QkM), I see that clang is indirect-failed because LLVM failed to build. Here is the LLVM build log: http://us-east.manta.joyent.com/pkgsrc/public/reports/Darwin/trunk/x86_64/20190128.1951//llvm-7.0.1/build.log

Now lots of things from lang/* seems to be failing to build for Darwin 20.6.0/x86_64:
https://bulktracker.appspot.com/build/ag1zfmJ1bGt0cmFja2VychILEgVidWlsZBiAgICZp9iICww/lang/

But the clang-13.0.1 looks OK here:
https://bulktracker.appspot.com/pkg/ag1zfmJ1bGt0cmFja2VyciILEgVidWlsZBiAgICZp9iICwwLEgNwa2cYgICAqYTEuggM

So judging by the pkgin, the issue is probably fixed.
I have no macOS to check the pkgsrc myself, though.

[sskras]

I guess the commit 19731f7 had nothing to do with this bug (and with closing it).

[jperkin]

clang is available in the macOS repositories, but it is strongly recommended to just use Apple's version either via XCode or Command Line Tools.