[Slackbuilds-users] Missing "lld" on x86 Slackware-15.0
fourtysixandtwo
fourtysixandtwo at sliderr.net
Sun Mar 1 19:36:47 UTC 2026
It's up to you, but I've gone with "i?86) ARCH=i686 ;;" for
cargo-vendor-filterer after the i586 issue was reported to me.
Support for i586 with rust is not high on their priority list.
https://doc.rust-lang.org/rustc/platform-support.html
If you do want to have it work, I would note the added dep in the
README and maybe an if statement in the slackbuild for that situation.
But I believe that there are not many i586 users for rust builds.
Cheers
On Sun, Mar 1, 2026 at 12:11 PM Shahab Vahedi via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:
>
> I need to pick your brain on something. There is this program
> called Bear that recently moved their code base from C++ to Rust.
> When building it, I noticed that the build fails on i586 version
> of Slackware-15.0 [1], but is fine on x86_64 variant.
>
> I have narrowed down the problem to missing "lld" binary on x86
> Slackware (llvm-13) [2]. Indeed, Slackware64-15.0's llvm package
> (llvm-13 again) provides the "lld" linker.
>
> At first I thought maybe I could get away with having a link
> from "lld" to "ld", but that was not a success [3]. The linking
> phase really needs the "lld" tool.
>
> I finally managed to have "lld" on x86 Slackware-15.0 by installing
> llvm-22.1 package from the "extra" repository. That package does
> provide the "lld" binary. Moreover, I was not in the mood for
> compiling "llvm-opt", so I did not try that, but I'm going to
> _assume_ that it also provides the "lld" tool.
>
> After having "lld" on the system, the build went just fine.
>
> To summarise the situation:
>
> 1. Bear builds fine on Slackware64-15.0 because there is lld
> 2. Bear faild to build on Slackware-15.0 since there's no lld
> 3. The linking process does really need lld (cannot be bypassed)
>
> Now, what should I do with this?
>
> - Shall I add "llvm-opt", to the "REQUIRES" field and explain
> in the README that is only needed for x86 variants? Please keep
> in mind that I actually haven't tried "llvm-opt" but the pre-built
> package of llvm-22.1 from the "extra" repository.
>
> - Should I create two separate packages (Bear vs Bear32)?
> I'm not in favour of this option.
>
> - Or maybe something else?
>
>
> -Shahab
>
> [1]
> https://github.com/SlackBuildsOrg/slackbuilds/pull/14530#issuecomment-3975967832
>
> [2]
> the problem manifests itself during the linking phase as
> note: collect2: fatal error: cannot find 'ld'
> compilation terminated.
> what actually is not found is "lld" and not "ld".
>
> [3]
> If "ld" is used instead of "lld", the "ld" will return an error
> /usr/bin/ld: anonymous version tag cannot be combined with other version tags
> collect2: error: ld returned 1 exit status
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
More information about the SlackBuilds-users
mailing list