Problems with kcfg files in amarok

Andras Mantia amantia at freemail.hu
Mon Jan 12 17:28:59 GMT 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You're right. Now IIRC #MIN_CONFIG(3.0) disables some HEAD features, including 
the kconfig_compiler. But maybe some kdenonbeta apps want to be runnable on 
KDE 3.0/3.1, so it can't be removed from there...

Andras

On Monday 12 January 2004 15:11, Anne-Marie Mahfouf wrote:
> On January 12, 2004 05:44 am, Andras Mantia wrote:
> > Hi,
> >
> >  Does anyone know why do I get this:
> >
> > make[1]: Entering directory
> > `/development/sources/kde-head/kdenonbeta/amarok/amarok' ./amarok.kcfg
> > ./amarokconfig.kcfgc; ret=$?; \
> > if test "$ret" != 0; then rm -f amarokconfig.h ; exit $ret ; fi
> > /bin/sh: line 1: ./amarok.kcfg: Permission denied
> > make[1]: *** [amarokconfig.h] Error 126
> > make[1]: Leaving directory
> > `/development/sources/kde-head/kdenonbeta/amarok/amarok' make: ***
> > [all-recursive] Error 1
>
> in configure.in.in in the kdenonbeta module,
> put
> #MIN_CONFIG
> as first line instead of the one you have
>
> cheers
>
> annma

- -- 
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFAAtlbTQdfac6L/08RAjviAKCjDJYijGhtphDapvjEAHoxWUVuwQCgiIMj
zLhKwQVrxPkx6iFWfuR4e2w=
=2BMm
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list