Re: Build for F2A85-M Foobared, any ideas?

[Paul Menzel]

Dear Keith,

Am 16.08.21 um 12:39 schrieb Keith Emery:
> I went one further and just deleted the whole working directory, 
> re-cloned coreboot and built using that exact configuration. All to 
> little avail.

Please do not leave the other questions/requests unanswered.
> How do I go about finding the exact commit that was used in the log?

It’s in the path name or logs in the directory I referenced: 
4.13-917-g192177d34d refers to commit hash 192177d34d.

Kind regards,

Paul

PS: It’s common to interleaved style when replying (on mailing lists).

Build for F2A85-M Foobared, any ideas?

[Keith Emery]

On 16/8/21 8:43 pm, Paul Menzel wrote:
> It’s in the path name or logs in the directory I referenced: 
> 4.13-917-g192177d34d refers to commit hash 192177d34d.

I've tried both hash's refrencing both sucessfull builds for 
F2A85-M board. I just get:

error: pathspec '192177d34d' did not match any file(s) known to git
         error: pathspec 'fdfc473380' did not match any file(s) known to git

Build for F2A85-M Foobared, any ideas?

[Peter Stuge]

Hi Keith,

Paul Menzel wrote:
> https://review.coreboot.org/plugins/gitiles/board-status/+/71278e2819996f2e6...

Keith Emery wrote:
> > It’s in the path name or logs in the directory I referenced: 
> > 4.13-917-g192177d34d refers to commit hash 192177d34d.
>
> I've tried both hash's refrencing both sucessfull builds for F2A85-M
> board. I just get:
>
> error: pathspec '192177d34d' did not match any file(s) known to git
>   error: pathspec 'fdfc473380' did not match any file(s) known to git

192177d34d is the commit locally on idwer's system at the time of
testing - it's possible that he had some minor changes on top of
the upstream code, resulting in a new commit.

Fortunately, this file:

https://review.coreboot.org/plugins/gitiles/board-status/+/71278e2819996f2e6...

Shows:

Upstream revision: 9a1b720b1f

And commit 9a1b720b1f is indeed some 950 commits ahead of the 4.13
tag, so I would try that out.

Kind regards

//Peter

Build for F2A85-M Foobared, any ideas?

[Keith Emery]

I tried the commit you suggested with the exact .config cut and pasted. 
However the make just dies with the following:

make: *** No rule to make target 
'src/commonlib/bsd/include/commonlib/bsd/cbfs_mdata.h', needed by 
'build/bootblock/commonlib/bsd/cbfs_mcache.o'.  Stop.

On 18/8/21 1:38 am, Peter Stuge wrote:
> Hi Keith,
>
> Paul Menzel wrote:
> > https://review.coreboot.org/plugins/gitiles/board-status/+/71278e2819996f2e6...
>
> Keith Emery wrote:
> > > It’s in the path name or logs in the directory I referenced:
> > > 4.13-917-g192177d34d refers to commit hash 192177d34d.
> >
> > I've tried both hash's refrencing both sucessfull builds for F2A85-M
> > board. I just get:
> >
> > error: pathspec '192177d34d' did not match any file(s) known to git
> >    error: pathspec 'fdfc473380' did not match any file(s) known to git
>
> 192177d34d is the commit locally on idwer's system at the time of
> testing - it's possible that he had some minor changes on top of
> the upstream code, resulting in a new commit.
>
> Fortunately, this file:
>
> https://review.coreboot.org/plugins/gitiles/board-status/+/71278e2819996f2e6...
>
> Shows:
>
> Upstream revision: 9a1b720b1f
>
> And commit 9a1b720b1f is indeed some 950 commits ahead of the 4.13
> tag, so I would try that out.
>
> Kind regards
>
> //Peter
> _______________________________________________
> coreboot mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]