[llvm-bugs] [Bug 40678] New: llvm-config generates options that are incompatible with clang++

via llvm-bugs llvm-bugs at lists.llvm.org
Sun Feb 10 01:09:52 PST 2019


https://bugs.llvm.org/show_bug.cgi?id=40678

            Bug ID: 40678
           Summary: llvm-config generates options that are incompatible
                    with clang++
           Product: clang
           Version: 7.0
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: Driver
          Assignee: unassignedclangbugs at nondot.org
          Reporter: michael.finn.jorgensen at gmail.com
                CC: llvm-bugs at lists.llvm.org, neeilans at live.com,
                    richard-llvm at metafoo.co.uk

Created attachment 21460
  --> https://bugs.llvm.org/attachment.cgi?id=21460&action=edit
Output from "llvm-config --cxxflags"

I have a minimal C++ file (named test.cc), and I try to compile it with clang++
and llvm-config.

I run the command:
clang++ `llvm-config --cxxflags` test.cc

This command fails with the error:
clang-7: error: unknown argument: '-fstack-clash-protection'

If I run "llvm-config --cxxflags" alone I see that the problematic option is
indeed part of the output. The full output is attached.

I believe this is an error, and that the options generated by the llvm-config
command should all be accepted by the clang++ command.


Additional information:

I can compile the given file test.cc without problems if I don't invoke
llvm-config, i.e. the following command works without error:
clang++ test.cc

The versions I'm using are: 7.0.1 for both clang++ and llvm-config.

I'm using Fedora 29 (64-bit).

P.S. This is all part of a large project (not my own) on github
(https://github.com/ghdl/ghdl).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190210/615e25dc/attachment-0001.html>


More information about the llvm-bugs mailing list