/usr/bin/gcc-ar vs /usr/bin/ar

[yesudeep]

Hello,

I’m wondering about the difference between /usr/bin/gcc-ar and /usr/bin/ar.
When using them with bazel, they exhibit different behavior.
One supports reading parameters from ‘@file’ and another doesn’t appear to:
bazel complains about this because when it uses the binary at /usr/bin/gcc-ar.
As soon as I sym-link /usr/bin/gcc-ar -> /usr/bin/ar, bazel works as expected).

Why are there 2 ‘ar’ binaries and can /usr/bin/gcc-ar be a symlink to
whatever we're using at /usr/bin/ar? I'm asking because as soon as there is
a system update the symlink is replaced automatically and I have to redo the
sym-linking.

Cheers,
Y.

[fenrus75]

gcc-ar is a wrapper around ar that adds support for LTO.... odd that there's any other difference at all beyond LTO support

…

On Fri, Jul 15, 2022, 20:00 Yesudeep Mangalapilly ***@***.***> wrote: Hello, I’m wondering about the difference between /usr/bin/gcc-ar and /usr/bin/ar . When using them with bazel <https://bazel.build/>, they exhibit different behavior. One supports reading parameters from ***@***.*** <https://github.com/file>’ and another doesn’t appear to: bazel complains about this because when it uses the binary at /usr/bin/gcc-ar. As soon as I sym-link /usr/bin/gcc-ar -> /usr/bin/ar, bazel works as expected). Why are there 2 ‘ar’ binaries and can /usr/bin/gcc-ar be a symlink to whatever we're using at /usr/bin/ar? I'm asking because as soon as there is a system update the symlink is replaced automatically and I have to redo the sym-linking. Cheers, Y. — Reply to this email directly, view it on GitHub <#2675>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJ54FJ6SVK4NRXHY34644DVUIQWLANCNFSM53XLCZNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[yesudeep]

Ah, I see. Reading more about this at: bazelbuild/bazel#3760

[yesudeep]

Closing this as this isn't as a result of clearlinux.

[yesudeep]

As a side note, I've had to replace /usr/bin/gcc-ar with a wrapper script as a workaround.
I guess I'll have to keep re-symlinking gcc-ar whenever it updates, but that's alright I guess.