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

Request: change to ghc-7.10.3 settings #3072

Closed
alanz opened this issue Mar 18, 2017 · 11 comments
Closed

Request: change to ghc-7.10.3 settings #3072

alanz opened this issue Mar 18, 2017 · 11 comments
Milestone

Comments

@alanz
Copy link
Contributor

alanz commented Mar 18, 2017

On ubuntu 16.10 and up, and debian testing, there is a linker problem under some circumstances:

https://ghc.haskell.org/trac/ghc/ticket/12147

This can be sorted out by changing the settings file for GHC 7.10.3 to

 ("C compiler flags", "-fno-PIE -fno-stack-protector -Wa,-mrelax-relocations=no"),
@borsboom
Copy link
Contributor

Is there a set of GHC bindist ./configure options or environment variables that will achieve that?

@alanz
Copy link
Contributor Author

alanz commented Mar 18, 2017

I have not idea. I just edited the file directly, after some discussion on IRC in #ghc

@borsboom
Copy link
Contributor

borsboom commented Mar 18, 2017

Stack should already be setting some no-pie options on Ubuntu 16.10 with GHC 7.10.3: https://github.com/fpco/stackage-content/blob/master/stack/stack-setup-2.yaml#L210

@alanz
Copy link
Contributor Author

alanz commented Mar 18, 2017

its not the no-pie, its the -Wa,-mrelax-relocations=no that is needed in this case.

@alanz
Copy link
Contributor Author

alanz commented Mar 18, 2017

In addition to the existing no-pie

@borsboom
Copy link
Contributor

borsboom commented Mar 19, 2017

@alanz Do you think those should be applied to all no-pie distros, or is this Ubuntu 16.10/debian testing specific? I try to avoid adding more platform variations unless necessary as each one increases the maintenance and testing burden.

@alanz
Copy link
Contributor Author

alanz commented Mar 19, 2017

I would imagine so. The original thread discussing this noted it on Arch Linux and Ubuntu, and I hit it on Debian testing. It is the underlying binutils or whatever that are used everywhere.

See the whole thread at DanielG/ghc-mod#762 (comment)

@borsboom
Copy link
Contributor

Can you try making a local copy of stack-setup-2.yaml, adjusting the configure options for the linux..-nopie variants as you see fit, and then use stack setup --stack-setup-yaml=<<PATH-TO-LOCAL-FILE>> to test it? You should move your current ~/.stack/programs out of the way first. If that works, please open a PR against the fpco/stackage-content repo with the changes.

@alanz
Copy link
Contributor Author

alanz commented Mar 27, 2017

I am travelling at the moment with bad connectivity. I will do this when I get back, early next week.

@decentral1se
Copy link
Member

Any updates @alanz?

@decentral1se decentral1se added this to the Support milestone Sep 17, 2017
@mpilgrem
Copy link
Member

I am closing this issue given the passage of time and because the master branch version of Stack does not support LTS < 12.0.

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

4 participants