Yep, you found my mistake =). I can't test it right now but one quick question - is it generally considered good to have two spec files for one package or could I just completely disregard the
"%use R_64 = R.spec" in this block: %ifarch amd64 sparcv9 %include arch64.inc %use R_64 = R.spec %endif ? Thanks, Brandon Barker Phone: (607) 262-6009 brandon.barker at gmail.com http://brandon.barker.googlepages.com/home On Mon, Aug 3, 2009 at 3:14 AM, Hemantha Holla<Hemantha.Holla at sun.com> wrote: > Brandon Barker wrote: >> >> I think I'm almost there, but I'm now getting Deep Recursion messages, and >> it looks like perl will eat up my memory if I don't kill it (after 2GB I >> kill it, as I have another long running process for work on this machine >> that I don't want to die). >> >> What is strange about this is that the recursions seem to be due to >> several things on their own: "%include base.inc" is one of them >> >> This is another: >> %ifarch amd64 sparcv9 >> %include arch64.inc >> %use R_64 = R.spec >> %endif >> >> > > You seem to using R.spec from inside R.spec i.e your R.spec has something > like > '%use R.spec' in it. That may be causing the recursion. > > Check SFEabiword.spec for example. SFEabiword.spec has the line > ? %use abiword = abiword.spec > > and abiword.spec is in the base-specs folder. > > $ ls spec-files-extra/base-specs/abiword.spec > spec-files-extra/base-specs/abiword.spec > > You could something similar by creating a differently named base-spec. > > > Hemantha > >
