Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: SooperLooper, a realtime software looping sampler 
(&Jack client)

------- Additional Comments From [EMAIL PROTECTED]  2006-08-02 13:42 EST -------
(In reply to comment #4)
> > (In reply to comment #2)
> > However i have question, when i saw build.log i found configure was called
> > nearly 5 times. What kind of this configuration script?
> Yes, I see that in my logs, I don't know what is triggering this. In my case 
> the
> build finishes successfully even with the warnings and repeated configure 
> calls.
>  And the software works. Weird. 
> (In reply to comment #3)
> > I think you should add NEWS,AUTHORS,Changelog files to your source code 
> > thru'
> > adding patch. then changes in %build
> > %build
> > # remove compiler option unrecognized by gcc4x
> > find . -type f -exec %{__perl} -p -i -e "s|-fmove-all-movables||g" {} \;
> > aclocal
> > autoheader
> > automake
> > autoconf
> > %configure
> > %{__make} %{?_smp_mflags}
> Hmmm, if I do this to try to fix things then a make does trigger the error 
> that
> Anthony sees. Of course if I run aclocal/automake as suggested the error 
> happens
> again. Buggy auto* scripts?

I had not realized that was there (that is what should be used in
these cases, I think). Running it managed to bring everything up to date with
the newer autotools versions and pointed to a missing build requirement

After adding that I'm getting a complete build with no configure repeats or
other warnings. I'll actually test the resulting packages and will post newer
.spec and srpms when done. 

Configure bugmail:
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

Fedora-package-review mailing list

Reply via email to