On Fri, Feb 21, 2014 at 9:16 AM, Kevin Fenzi <kevin@scrye.com> wrote:
On Fri, 21 Feb 2014 08:28:24 -0700Ah, that makes more sense...
Dave Johansen <davejohansen@gmail.com> wrote:
>
> Doh! The original email in this chain was a copy and paste/stupid user
> error on my part. No, I no longer get that issue with the llvm build
> and like Kevin pointed out, just waiting worked.
>
> But I sent two emails this month with very similar titles and I
> accidentally copied the wrong one in the original email. The correct
> one is
> https://lists.fedoraproject.org/pipermail/devel/2014-February/195687.htmland
> the failed build is
> http://koji.fedoraproject.org/koji/taskinfo?taskID=6542755 with an
> issue during the creation of the source rpm. Any ideas on what may be
> causing this?
So, in that build:
DEBUG util.py:281: Downloading qt-creator-opensource-src-3.0.1.tar.gz
DEBUG util.py:281: error: Unable to open /builddir/build/SOURCES/qt-creator-Fedora-privlibs: No such file or directory
DEBUG util.py:281: error: query of specfile qt-creator.spec failed, can't parse
DEBUG util.py:281: Could not execute sources: Could not parse the spec, exited 1
DEBUG util.py:371: Child return code was: 1So, you were missing a sources file. It seems after that you commented that out,
however the build then failed due to a ppc64 issue.
make[3]: *** [.obj/release-shared/botan.o] Error 1
not sure what is causing that off hand...The source wasn't missing, but was causing the source rpm to not complete for some reason, so I tried commenting it out to see if that would allow the source rpm to build correctly (which it did), but like you said now it's getting a build error on ppc64. I've never tried building on ppc64 before, so I assumed it would work, but maybe there's something that needs to be worked out there.