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

SIGUNUSED vs SIGSYS #131

Open
addeps3 opened this issue Jan 20, 2018 · 3 comments
Open

SIGUNUSED vs SIGSYS #131

addeps3 opened this issue Jan 20, 2018 · 3 comments

Comments

@addeps3
Copy link

addeps3 commented Jan 20, 2018

(had to rewrite this from earlier)
I'll submit this report here.

Compiling fails if src/pty.c:302 contains for (i = 1; i < SIGUNUSED; ++i) instead of for for (i = 1; i < SIGSYS; ++i) on some systems, such as Arch Linux because that signal seems to have a different name.

Wikipedia calls the two synonymous

Compilation finishes and kmscon runs well afterwards.

jonnrb added a commit to jonnrb/kmscon that referenced this issue Jan 20, 2018
@Aetf
Copy link

Aetf commented Jan 24, 2018

You could try my fork, which fixes this and a few other things. And this is an updated version of its dependency: libtsm.

@cirosantilli
Copy link

@Aetf yours failed with:

/home/ciro/git/kmscon/src/kmscon_terminal.c:105: undefined reference to `tsm_vte_get_def_attr'

on Ubuntu 18.04.

I recommend enabling the issue tracker there.

@Aetf
Copy link

Aetf commented May 28, 2018

@cirosantilli

Oh somehow I didn't notice I've disabled the issue tracker. Please move the discussion there: Aetf#2

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