-
Notifications
You must be signed in to change notification settings - Fork 318
Build fails on ArchLinux #26
Comments
Same happens to me, on both branches i3-gaps and i3-gaps-next |
Two people on reddit reported the same. One of them could fix it again later, for no apparent reason (http://www.reddit.com/r/unixporn/comments/2qkdfm/i3_with_gaps_m_and_no_status_bar/cn7jeew). Could you please try compiling vanilla i3? I have no clue on why this would be an issue of my fork. If you can't compile vanilla i3 either, it's an i3 issue.
It could be a compiler issue. You definitely need gcc to compile it. I've compiled it successfully on Manjaro before, haven't tried it on Arch yet. |
vanilla i3 compiles fine for me, trying to compile your branch gives me the same error as @skoftoby but the first line is this one:
not sure if it's relevant, running gcc --version outputs
|
Vanilla i3 builds and runs perfectly fine, gcc version is the same as @ninja-coding's. |
I think this might have something to do with the fact that I deleted all tags. Can someone try adding a tag to the latest commit (just for the sake of having one) and building again? |
Removing all tags locally, I can reproduce the issue. You can fix it by running a dummy |
Pardon my ignorance, but what exactly does adding the tags do that makes it compile alright? |
|
Yes, but why does that help? I can't see how adding tags makes it compile. |
It compiled fine adding a tag, this is so weird |
i3 compiles a version string and the like. For this it uses Now, the make process will set some (environment / compile?) variables which due to the failed command are empty. This causes the compilation of the macro to fail. |
I just merged and pushed all upstream tags. You should probably remove the fake tag again. |
Ran into the same problem, the cause was that older (in my case, 1.8.3) git versions do not recognise the -C option. |
When building i3-gaps-git from the AUR, the build process fails at ipc.c with the following error(s):
The same occurs when building from a cloned repository.
The text was updated successfully, but these errors were encountered: