|
From: | mark carter |
Subject: | Compilation update |
Date: | Fri, 24 Mar 2017 11:21:37 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 |
Marcin, As you point out, neoleo is hosted athttps://github.com/blippy/neoleo rather than on gnu. I have taken a look at your CVS repo, done some hacking, and I have been able to compile oleo! It runs! I do not have things in a suitable form for a patch, but here is an overview of the results of my investigations so far: src/Markefile.am:8 Need to get rid of `../lib/ansi2knr' Googling around, this seems to way to convert ANSI C definitions to K&R (Kernighan and Ritchie "traditional C"). I'm happy to drop that, as nobody should be using such an antiquated compiler doc/*texi compilation fails The fixes for these are pretty trivial and non-controversial. libxp autoreconf has a problem with LT_HAVE_LIBXP. I have commented it out for now, and was able to obtain a build. However, the root cause appears to be "underquoting" in m4/xp.m4. My knowledge `m4' is practically non-existent, but I will take a look to see if I can fix whatever seems to be the problem. So, in summary, it should be too difficult to get oleo working again. I'm not sure if you are aware, but there is apparently a patch for oleo here: https://launchpadlibrarian.net/19062178/oleo_1.99.16-11.diff.gz It seems to patch the tar distribution: `configuration' in particular. So although it's not exactly what we want, it's worth noting its existence. On Arch Linux, there seems to be a recent attempt at building oleo: https://aur.archlinux.org/packages/oleo/ I had only just noticed it, so I don't know what the status of it is. I know that there were build problems in the past. I might liaise with the package maintainer to see what's going on. |
[Prev in Thread] | Current Thread | [Next in Thread] |