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.

Sign up for GitHub

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

Jump to bottom

Use response files when possible to communicate with gcc (and ld) #22

Closed
gbaz opened this issue Mar 7, 2019 · 1 comment · Fixed by #23
Closed

Use response files when possible to communicate with gcc (and ld) #22

gbaz opened this issue Mar 7, 2019 · 1 comment · Fixed by #23

Comments

@gbaz
Copy link
Contributor

gbaz commented Mar 7, 2019

c2hs processes response files correctly as of #9 and the fixes in a816333 and 8807b4c as far as I know. But from review of the code it doesn't look to me like it uses them to communicate with the c compiler itself?

I've run into issues with nix, which can generate absurdly long flag arguments, which I think would be fixed if this were improved.
@gbaz
Copy link
Contributor Author

gbaz commented Mar 7, 2019

it appears that ghc always assumes compilers and linkers support response files, so likely we can do the same here and we're "no worse"

@gbaz gbaz changed the title Use response files when possible to communicate with gcc Use response files when possible to communicate with gcc (and ld) Mar 7, 2019
@gbaz gbaz mentioned this issue Mar 7, 2019
Open
@cdepillabout cdepillabout mentioned this issue Mar 8, 2019
Open
@gbaz gbaz mentioned this issue Mar 8, 2019
Merged
@gbaz gbaz closed this as completed in #23 Aug 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

response file generation and usage haskell/hsc2hs
1 participant
@gbaz