On Tue, Dec 30, 2008 at 06:14:54PM -0200, Paulo Cavalcanti wrote: > On Tue, Dec 30, 2008 at 4:45 AM, Axel Thimm <[email protected]> wrote: > > On Mon, Dec 29, 2008 at 07:18:29PM +0100, Alexander 'Leo' Bergolth wrote: > > > On F10, there seems to be a macro expansion loop in macros.kmdl. (See > > > the error below.) > > > > it's not a loop, it is indeed too limited macro expansion. If I > > remember correctly rpm uses more than 1 (I think 4) stack slots for > > one invocation, so you can already hit the limit with a couple > > complicated macros. > > > > > The error seems to be related to the definition of kmdl_name: > > > > > > Using > > > rpmbuild --define 'kmdl_userland 1' --define 'kmdl_name x' ... > > > or > > > rpmbuild --define 'kmdl_name x' ... > > > > > > works fine but > > > > > > rpmbuild --define 'kmdl_userland 1' --define '_kpkgname x' ... > > > > > > ... also shows the max-recursion error. > > > > Defining kmdl_kernelsrcdir also works. > > > > Please do something of the above for now as a temporary > > workaround. The true fix would be to allow rpm to be more generously, > > and the long term workaround would be to manually expand some of the > > macros or even use $global ... %{expand:%{exec...}} style definitions.
> If I use in F10 (with its new rpm package) > > rpm -ivh alsa-driver-1.0.18-70.fc8.src.rpm > > and then do a > > rpmbuild -bs --rmsource alsa-driver.spec > > I see the recursion problem. Please, note that > I am just recreating the .src.rpm. Nothing more. Yes, I didn't say it's only applying to kmdls, it applies to any rpmbuild operation. :( I just didn't see it until now as my buildsystem fills out many of the macros in advance (with --define ...) so rpmbuild doesn't need to expand the macros itself. -- Axel.Thimm at ATrpms.net
pgpDvOnKrGUx8.pgp
Description: PGP signature
_______________________________________________ atrpms-devel mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-devel
