Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] boot/opensbi: unconditionally disable SSP
Date: Wed, 12 May 2021 20:55:00 +0200	[thread overview]
Message-ID: <87o8dfkcjf.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAOCHtYhAabRzQMEfLpY=mMOuazHeP-b6WmmXTcTLLnG+5KeqMw@mail.gmail.com> (Robert Nelson's message of "Wed, 12 May 2021 07:45:17 -0500")

>>>>> "Robert" == Robert Nelson <robertcnelson@gmail.com> writes:

Hi,

 > Just a heads up, our BeagleBoard.org CI triggered a build failure
 > after this commit last night..

 > ```
 > make distclean
 > make beaglev_defconfig
 > make -j8
 > ```

 > /mnt/storage/var/lib/jenkins/workspace/buildroot_beaglev_defconfig/output/build/opensbi-custom
 >   -xf -
 >>>> opensbi custom Patching

 > Applying 0001-Makefile-Don-t-specify-mabi-or-march.patch using patch:
 > patching file Makefile
 > Hunk #1 succeeded at 206 with fuzz 1 (offset 61 lines).
 > Hunk #2 succeeded at 219 with fuzz 1 (offset 62 lines).

 > Applying 0002-Makefile-unconditionally-disable-SSP.patch using patch:
 > patching file Makefile
 > Hunk #1 succeeded at 203 with fuzz 1.
 > Hunk #2 FAILED at 217.
 > Hunk #3 succeeded at 234 (offset -2 lines).
 > 1 out of 3 hunks FAILED -- saving rejects to file Makefile.rej
 > make: *** [package/pkg-generic.mk:209:

Ahh, that was what I was afraid of. I've sent a series to fix it:

https://patchwork.ozlabs.org/project/buildroot/list/?series=243398

In fact I did test beaglev_defconfig after adding
0002-Makefile-unconditionally-disable-SSP.patch using patch, but looking
back in my shell history I see I tested in a tree where the above series
is applied.

I'll get it fixed.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2021-05-12 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  7:43 [Buildroot] [git commit] boot/opensbi: unconditionally disable SSP Peter Korsgaard
2021-05-12 12:45 ` Robert Nelson
2021-05-12 18:55   ` Peter Korsgaard [this message]
2021-05-12 19:29     ` Robert Nelson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o8dfkcjf.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox