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

Some platforms might need -ltinfo #17

Closed
jtdaugherty opened this issue Sep 1, 2016 · 2 comments
Closed

Some platforms might need -ltinfo #17

jtdaugherty opened this issue Sep 1, 2016 · 2 comments

Comments

@jtdaugherty
Copy link
Collaborator

A user of my brick library (which uses vty, which uses terminfo) has reported this issue:

jtdaugherty/brick#75

Doing a little digging, it appears that this might be a general problem with some platforms where libncurses isn't linked with libtinfo. Although this report mentions a potential hotfix,

ponylang/ponyc#252

I am wondering if it makes sense to just add tinfo to the linker step for the Haskell terminfo package. Thoughts?

CC @sireeni

@judah
Copy link
Collaborator

judah commented Sep 1, 2016

The terminfo package already specifies -ltinfo if it finds libtinfo:
https://github.com/judah/terminfo/blob/master/configure.ac#L42

Furthermore, the Haskell terminfo is usually distributed as part of GHC (since it's needed to build the compiler). You can see in the referenced error-brick.txt that it doesn't build a new version of terminfo, so it's using the built-in one.

One way that error could happen is if there's a mismatch between the system on which GHC was built (which had tinfo) and the one where it's run (which doesn't). Does that make sense?

@jtdaugherty
Copy link
Collaborator Author

Yeah, I think that makes sense. I don't know where the user got their GHC distribution, but it's definitely possible it was built on a machine that different a different linking environment than the one in which they ran the build (and apparently they're on a Gentoo variant, so that's at least consistent with other reports of this error). They've been happy with the Gentoo hotfix for this, so I'm not sure there's much else to be done on this ticket. Thank you!

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

2 participants