so what you got there with /usr/lib/pd and doc/ in there ??
who does that belong to to whatever ..check it out and emerge --resume
then ..
ah, seems you got FEATURES=userpriv - so you might diasable thet .. but
seems actually this a bug in the ebuild , it shouldn't try making that
directory at
so what you got there with /usr/lib/pd and doc/ in there ??
who does that belong to to whatever ..check it out and emerge --resume
then ..
no way-.-
ah, seems you got FEATURES=userpriv - so you might diasable thet .. but
seems actually this a bug in the ebuild , it shouldn't try making
the Makefiles in the pd CVS tree are very are definetly not good.
they needs fixing globaly.
who is responsible for the CVS ?
i think that all of them have to be generalised ,so we can easiely build
anything.
i do everything manually on my system,
cause quite a few makefiles try to use -m32 in
[EMAIL PROTECTED] wrote:
the Makefiles in the pd CVS tree are very are definetly not good.
they needs fixing globaly.
who is responsible for the CVS ?
nobody.
the authors are responsible for their stuff.
so: if zexy/src/Makefile is broken, it is my fault...
i think that all of them have
the Makefiles in the pd CVS tree are very are definetly not good.
they needs fixing globaly.
who is responsible for the CVS ?
i think that all of them have to be generalised ,so we can easiely build
anything.
i do everything manually on my system,
cause quite a few makefiles try to use
On Tue, Nov 20, 2007 at 01:56:19PM +0100, IOhannes m zmoelnig wrote:
[EMAIL PROTECTED] wrote:
the Makefiles in the pd CVS tree are very are definetly not good.
they needs fixing globaly.
who is responsible for the CVS ?
nobody.
the authors are responsible for their stuff.
so: if
On Tue, Nov 20, 2007 at 04:59:18PM +0100, [EMAIL PROTECTED] wrote:
heh, it would be a definitely GOOD THING to tidy up our build systems.
but HOW?
i think of having one Makeglobal which will contain DESTDIR, CFALGS ,
*FLAGS ..etc all the general variebles.. and procedures (or how do you
[EMAIL PROTECTED] wrote:
also there is acouple of external which have duplicated objects.
what do you mean here?
nameclashes? duplicated functionality? aliases?
yeah ..i can't remenber, but when i used my strategy:
#'
foreach pde (`find -iname '*.pd_linux'`)
ln -s $pde
The Pd-extended Makefiles do use DESTDIR, CFLAGS, etc. but are only
somewhat hierarchical. That stuff could be greatly improved for
sure. Patches welcome :D
I think that it autoconf/config.h should be the technique for
handling libs and other dependencies. Perhaps automake would be
