On Tue, Aug 18, 2020, 02:15 Laura Abbott<laura@xxxxxxxxxxxx> wrote:
On 8/17/20 7:36 PM, Germano Massullo wrote:
> Hi there, I would need help in understanding why this kernel build failed.
>
> https://copr.fedorainfracloud.org/coprs/germano/kernel_204253_comment_14_patch/build/1613735/
>
> The SRPM is the same of Fedora repository except for a small patch file
> that I have added to run some tests against blk-mq scheduler
> https://bugzilla.kernel.org/show_bug.cgi?id=204253#c14
>
> The only errors I can see are like "Macro expanded in comment", but as I
> said, these expanded macros were already present in official Fedora
> build, so I don't understand why the build fails on my Copr repository.
>
> Thank you
From your log:
Applying: PCI: Add MCFG quirks for Tegra194 host controllers
Applying: Work around for gcc bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96377
Applying:
error: Bad exit status from /var/tmp/rpm-tmp.FxtIcw (%prep)
That `Applying :` with nothing after it is suspicious. I'm guessing
the patch isn't being specified correctly in the .spec file.
Looks like git is used to apply the patches, but the new patch file is missing "Subject" and "From" headers, as they would be generated by git format-patch.
Fabio
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
