Skip to content

Add Arch Linux AUR packaging for eld#823

Draft
androm3da wants to merge 2 commits intoqualcomm:mainfrom
androm3da:bcain/arch_pkg
Draft

Add Arch Linux AUR packaging for eld#823
androm3da wants to merge 2 commits intoqualcomm:mainfrom
androm3da:bcain/arch_pkg

Conversation

@androm3da
Copy link
Contributor

No description provided.

Add PKGBUILD, .SRCINFO, and README for submitting eld to the Arch User
Repository. Build-tested against LLVM release/21.x with eld v21.1.8.

Key details:
- Builds eld within the LLVM source tree (required by eld's build system)
- Targets: ARM, AArch64, RISCV, Hexagon, x86_64
- Installs ld.eld binary, libLW.so plugin API, headers, and templates

Signed-off-by: Brian Cain <brian.cain@oss.qualcomm.com>
Runs on tag creation (v*) using an archlinux:latest container.
Derives the matching LLVM release/N.x branch from the tag's major
version, builds eld targets, and verifies all expected outputs exist.
No binary artifacts are published.

Signed-off-by: Brian Cain <brian.cain@oss.qualcomm.com>
@androm3da androm3da marked this pull request as draft February 13, 2026 04:51
@androm3da
Copy link
Contributor Author

FIXME/TODO:

  • maintainer email address
  • use v22.1.0 final tag for llvm or just the matching -rc?

@parth-07
Copy link
Contributor

use v22.1.0 final tag for llvm or just the matching -rc?

It seems that the eld v22.1.0-rc3 tag (added 2 hours ago) and the LLVM llvmorg-22.1.0-rc3 (added 3 days ago) are not in-sync. It is possible that the eld build may fail if we use llvmorg-22.1.0-rc3 because the eld v22.1.0-rc3 version was built using the LLVM release/22.x branch tip.

Perhaps in the future we should ensure that eld minor versions are compatible with the corresponding LLVM minor versions.

For now, I think we can use the matching -rc versions. Most likely the build should be fine. If it does not, we then need to either fix the eld v22.1.0-rc3 to be compatible with the corresponding LLVM tag, or explicitly use a good commit...

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