Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slim down devel/llvm11 #337

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Conversation

brooksdavis
Copy link
Contributor

This set of patches removes consumers of devel/llvm11 where possible (most didn't actually use it), removes if from USES=compiler and USES=llvm, and pares the default build down to just building the core LLVM bits. Unfortunately, it's used to bootstrap old ghc versions on aarch64 and armv7 so we're stuck with it for now, but we can cut its size dramatically.

The specified minimum version (11) is the current minimum so remove the
specification entiterly in preparation for removing support for llvm11
from Uses/llvm.mk.
This matches LLVM_DEFAULT which is what audio/faust will default to.
This is wrong as audio/faust uses USES=llvm:min=15,lib and thus might
use a version other than 15, but it's less wrong than hardcoding 11 and
the result compiles...
Bump _LLVM_MINVER to 12 and remove 11 from the valid list.  No remaining
ports depend on USES=llvm supporting 11 so remove support to allow the
port to be further slimmed down.
It's no longer possible for LLVM_DEFAULT to be 11 so remove support for
it.
Sponsored by:	DARPA, AFRL
I belive the only consumers of this port are lang/ghc810 and lang/ghc92
which use LLVM as part of the boostrap on armv7 and aarch64.  As such it
makes no sense to build anything by the native backend and the core LLVM
framework.

As an intial test of this hypothesis, deselect all standard options and
default to BE_NATIVE.  After a period of testing I plan to remove or
completely disable other options and restrict the set of architectures
that build llvm11 to reduce project resource use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants