Clang toolchain type should not be bound with LLD

[Julian Waters]

Hi!

I believe it's not a hard requirement that special variables can't be used,
just that it's strongly discouraged in favour of configure options. I'm not
sure if we support linker combinations other than the one the compiler
comes with, the extent of my knowledge is that I think Oracle uses gold for
gcc, but regardless you'd have to ask Magnus for that. But the issue is
still that different linkers might need to be treated differently by the
build system, and it might not yet be prepared to use linkers like mold
instead of lld

best regards,
Julian

On Wed, Jan 22, 2025 at 5:54 PM Bingwu Zhang <xtex at envs.net> wrote:

> Hi!
>
> The patch I mentioned in last message will first try to resolve the full,
> absolute path of lld, and use --ld-path to pass the path to Clang. It
> should
> have the same effect as passing -fuse-ld=lld. If it failed to do so, it
> will
> fallback to use -fuse-ld=lld to let Clang pick up the proper linker.
>
> btw it seems that CC and CXX is picked by the build system [1]. Why don't
> we
> just pick up the variable?
>
> I will later change it to use a configure option. How about
> --with-linker-path?
>
> Thanks! :)
>
> [1] https://github.com/magicus/jdk/blob/
> a62a870150cf199f16277b478af2f5d937255b3c/make/autoconf/toolchain.m4#L430
>
> --
> Bingwu Zhang
> xtex @ Wed, 22 Jan 2025 09:45:35 +0000
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/build-dev/attachments/20250122/2fe4ac84/attachment.htm>