diff options
| author | Raphael Isemann <teemperor@gmail.com> | 2020-05-29 17:08:28 +0200 |
|---|---|---|
| committer | Raphael Isemann <teemperor@gmail.com> | 2020-05-30 18:05:16 +0200 |
| commit | fd0ab3b3eb88de3fe4792c34b50084595e22d68d (patch) | |
| tree | 61fafd3006d2616cff7191cbecdf293a4b55a407 /llvm/tools/llvm-objdump/llvm-objdump.cpp | |
| parent | d99a1848c4f8ca164c0c0768e10eafc850b2a68a (diff) | |
| download | llvm-fd0ab3b3eb88de3fe4792c34b50084595e22d68d.zip llvm-fd0ab3b3eb88de3fe4792c34b50084595e22d68d.tar.gz llvm-fd0ab3b3eb88de3fe4792c34b50084595e22d68d.tar.bz2 | |
[lldb] Pass -fPIC flag even when DYLIB_ONLY is set
Summary:
It seems that when we rewrite a few rules to only build a dylib (i.e., when DYLIB_ONLY is set),
the rule for setting the CFLAGS for the dylib's object file compilation will no longer work. From what I can
see this is because in DYLIB_ONLY mode we pretend to compile the main executable so
the DYLIB_OBJECTS scope is actually never used.
This patch makes `-fPIC` unstopped if DYLIB_ONLY is set so that -fPIC actually ends up in the
CFLAGS for the dylib object file compilation.
The test for this is D80798 which only compiles on Linux with this patch.
Reviewers: friss, labath
Reviewed By: friss
Subscribers: JDevlieghere
Differential Revision: https://reviews.llvm.org/D80789
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions