Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

llvm-base's configure step produces inconsistent linker flags #58

Open
NathanHowell opened this issue May 17, 2013 · 3 comments
Open

llvm-base's configure step produces inconsistent linker flags #58

NathanHowell opened this issue May 17, 2013 · 3 comments

Comments

@NathanHowell
Copy link
Collaborator

If the library search path and regular PATH variables point to different versions of LLVM the package configuration file will point to multiple versions of LLVM.

See http://projects.haskell.org/pipermail/haskell-llvm/2013-May/000327.html for details.

@amigalemming
Copy link

I think that llvm-base should exclusively ask 'llvm-config'. However I know there were issues with llvm-config mixing dynamic and static libraries in its answers. That's why configure.ac had code to filter some files out.

@Ralith
Copy link
Collaborator

Ralith commented Jun 10, 2013

A pure llvm-config approach has been implemented for Windows support in 1f9574d, and appears to function adequately. In light of that, I think we should revisit the decision to use autoconf on other platforms.

@amigalemming
Copy link

On Mon, 10 Jun 2013, Benjamin Saunders wrote:

A pure llvm-config approach has been implemented for Windows support,
and appears to function adequately.

How does it work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants