Possible regression between 6.4.0 and 7.x: cc_library does not propagate linkopts option

[femshima]

Description of the bug:

Hello. It seems that Bazel 7.x does not link library specified in linkopts of dependency, even though 6.4.0 do.

For example, the following code, which creates libtest.so, should link to libuim.so as specified in uim dependency. However, in 7.x, it does not link.

# BUILD.bazel

cc_library(
    name = "uim",
    hdrs = glob([
        "usr/include/uim/**"
    ]),
    copts = [
        ""
    ],
    includes = [
        "usr/include/uim"
    ],
    linkopts = [
        "-luim",
        "-luim-scm"
    ],
)

cc_library(
    name = "test_lib",
    srcs = ["test.cc"],
    deps = [
        ":uim",
    ]
)

cc_shared_library(
    name = "test",
    roots = ["test_lib"],
)

I confirmed that by executing ldd, and also looking at libtest.so-2.params file. When built with 7.x, the libtest.so-2.params file does not include -luim or -luim-scm line.

Also, when I copy linkopts to test_lib, it works fine.

cc_library(
    name = "test_lib",
    srcs = ["test.cc"],
    deps = [
        ":uim",
-   ]
+   ],
+   linkopts = [
+       "-luim",
+       "-luim-scm"
+   ],
)

Which category does this issue belong to?

C++ Rules

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

1. Create WORKSPACE.bazel and MODULE.bazel.
2. Create BUILD.bazel posted above.
3. Create empty test.cc.
4. Run bazel build test --experimental_cc_shared_library in either bazel 6.4.0 or 7.2.1.
5. Check if src/bazel-bin/libtest.so-2.params contains -luim or -luim-scm.

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

release 7.2.1 (used bazelisk)

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

I tried to run bisect but failed, because 6.4.0 (good Bazel commit) is not an ancestor of 7.2.1 (bad Bazel commit), and their merge base commit fails to run.

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

[fmeum]

@oquenchil Is it possible that cc_shared_library now drops targets that don't contribute anything linkable (except linkopts)?

[fmeum]

@bazel-io flag

[oquenchil]

Probably broken by #20228 which fixed #19920.

The fix for this one would probably be to simply take the linkopts from the linker_input containing no libraries then discard it, so that it doesn't throw errors about it not being exported.

[keith]

#21884

[iancha1992]

@bazel-io fork 7.4.0

[comius]

Duplicate of #21884