-
Notifications
You must be signed in to change notification settings - Fork 17
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
Compilation error #52
Comments
Someone else had this problem. I'll look into it. I'm not directly using libabsl, so I don't know where the requirement for that library is coming from at the moment. |
Could you tell me what distro you are using? |
I am on arch, btw.
Did a little research and apparently, on Arch Linux, the package |
Ok. Good to know. Checkout the linker arguments in this PR. That should fix the problem. I'll have to think about how to add this in a distribution specific way. I reverted out the PR because it doesn't work on Ubuntu. |
Had same problem, and this fixed issue for me, thanks. I'm also using arch |
Thanks! It did solve the problem here, but now i can't actually execute the program (lol), the output says it's looking for things on |
are you using startx or your login manager to run it ? |
startx, i've have configured it the way it's specified on the README, if i run in normal mode, it simply go back to login, but if i run on develop mode it starts to keep showing these error logs that i've mentioned. |
oh can you share the errors? |
Hello all. Would someone with this libabsl error test this branch out to see if it works with arch linux? |
I have tested it. It compiled successfully but I cant get it to run (using startx). I launched my system without any display manager, logged in (using tty) and launched |
did you add cd as well in the .xinitrc file make sure it's correct like in the readme & can you share what's the error? |
What I got after the black screen:
I don't get an error or anything which is strange. The log file at "/home/vuln/.local/share/xorg/Xorg.1.log" does not really contain any valuable information and does not seem to contain any errors (Any (EE) before the lines). my
The Are there any other locations where I can check the logs for errors? |
Is the log file not located at |
Thats probably because I messed up the cd command once. (but fixed it afterwards) The contents of
For some reason terminator does not work because of something unrelated, so I launched my other terminal I cd into the HackMatrix directory and launch
After that I got this error:
|
It is interesting that my XServer doesn't throw a bad atom but yours does. The atom was certainly bad. I just merged a PR. Pull master and the bad atom crash should at least be fixed. |
The bad atom error is now fixed, and HackMatrix started. What works:
The issues I encounter:
The outputted error after crash is:
|
Ok. Looks like a limitation of GLSL I didn't know about in some OpenGl implementations and I'll have to change the shaders to accommodate. I'll make a PR for it soon. |
I tried it and it launched :) I can move around, things get rendered, but when I press v to launch dmenu, the wm crashes. (like issue #57) note: when I lauch |
Hmmm. I can't reproduce on my machine so I personally won't be able to backtrace the segfault. Do you know how to switch TTY and use tmux/gdb? The way I debug segfaults is the following:
In terminal 1:
In terminal 2:
In terminal 1 (may need to press ctrl+b to get ther):
Any part of the stack trace that is from /src should be relevant. |
I know how to swich TTYs (in case a wm crashes or im testing a wm like yours) but I have never used debugging tools like tmux or gdb. This could be a great opportunity to learn about those debuggers. |
Ok. Cool! gdb is pretty useful. I wrapped this one in a debugger script because it needs a DISPLAY environment variable to connect properly. If the matrix X session isn't the first session started on bootup (IE you started it on TTY2) then you may need to change the DISPLAY to = 2 in that devtools/gdb script. You can also run it from a terminal in another wm if you don't want to use a raw TTY (which will help you copy and paste the backtrace). I also have a logging ticket that I will work on soon that should print the backtrace in the logs. |
I also had this issue, and I'm using Void Linux, musl edition. I also had to set |
Hey there, i am trying to compile the program on Arch but i am facing theses error after running
make
:I know some bits are in portuguese, but they are basically saying "undefined reference at symbol" and "error adding symbols: DSO missing from command line"
I've already checked if the libraries were installed, maybe there is a missing library on the README code example?
The text was updated successfully, but these errors were encountered: