Hello!
I am trying to build the current state of the git repo on Fedora 44. I got up to making the documentation, at which point everything grinds to a halt. After piping stderr to a separate file so I can actually read it all, it appears that the build script did not wrap the path in quotes, and thus created a bunch of broken nonsense that led to over 200 errors, causing the build to fail with error 255. Which is... very surprising for a multitude of reasons. The biggest one being that it was using the non-symlinked path, which contains spaces, when I was executing it from a symlinked path that had no spaces. But also, everything else up to that point built just fine...
I relocated my local copy of the repository to a completely different location on a completely different drive to ensure that there were no spaces in the path, and the build seems to have completed successfully.
Hi, what "script" are you talking about?
Ah, right, I'm talking about the Makefile. In particular, the ones in cde/doc/en_US.UTF-8/guides
To elaborate, I put the majority of my files on my computer in a 27TB HDD that I named "Storage Barn DX", because I am very much allowed to have a fun name for a behemoth HDD. This means the mount point is
/mnt/Storage Barn DXand changing the name would break, uh, everything that looks for things on this drive. Now on the root of this drive is a folder I call "GITS" where I put all git-related stuff: various cloned repos and all my local repos, basically. To make it easier to get into from launching a fresh terminal, I created a symlink in my home directory to this location, so~/GITSis a valid alternative to/mnt/Storage Barn DX/GITS. However, configure.sh prefers the non-symlinked path.Thus, when the Makefile for CDE gets to making the guides, this happens:
And when you look at the first few lines of what went to stderr, the cause is simply not wrapping the path, thus shattering the command into multiple bad commands. But I don't know exactly where in the Makefile (or which Makefile) I would need to fix this. Yes, the problem can be "fixed" by using a different directory that doesn't have spaces in the path, but considering that everything else up to this point builds just fine, it would be better to amend the Makefiles to not have this be an issue.