On Mon, May 24, 2010 at 09:42:06PM +0200, Thomas Dahms wrote:
Sorry, minor typo. It should be fixed. How is the PKGBUILD broken? It
works fine for me.
It will probably work if you have a local clone of the repo and just
do a makepkg therein.
If you look at it like the average user that tries
Sorry, minor typo. It should be fixed. How is the PKGBUILD broken? It
works fine for me.
It will probably work if you have a local clone of the repo and just do
a makepkg therein.
If you look at it like the average user that tries to build a package,
it works only when you already cloned the
On Mon, May 24, 2010 at 09:03:29PM +0200, Thomas Dahms wrote:
Hi,
Am 24.05.2010 14:38, schrieb Kris Maglione:
Not quite. It installs it to $(LIBDIR)/../../lib. It looks like it's
always been a bug, which just happened to be copacetic when the libs
were held in ../lib instead of ../../lib.
The
Hi,
Am 24.05.2010 14:38, schrieb Kris Maglione:
Not quite. It installs it to $(LIBDIR)/../../lib. It looks like it's
always been a bug, which just happened to be copacetic when the libs
were held in ../lib instead of ../../lib.
The fix for wmii brings up a new problem (see below). This happens
On Mon, 24 May 2010 12:56:05 +0200
Thomas Dahms wrote:
> Hi,
>
> the recent Makefile changes will install the libs always to /lib
> instead of $(PREFIX)/lib. Looking in /lib, I also found
> libwmii_hack.so there, so wmii probably has the same issue.
>
> Also DESTDIR seems to be completely ignor
Hi,
the recent Makefile changes will install the libs always to /lib instead
of $(PREFIX)/lib. Looking in /lib, I also found libwmii_hack.so there,
so wmii probably has the same issue.
Also DESTDIR seems to be completely ignored.
--
Thomas Dahms
