Re: Broken build on OpenBSD

2021-03-07 Thread Mark Kettenis
> Date: Mon, 1 Mar 2021 09:02:18 -0500 > From: Tom Rini > > On Tue, Feb 23, 2021 at 08:07:21PM +0100, Mark Kettenis wrote: > > > Hi Simon, > > > > Commit c5819701a3de61e2ba2ef7ad0b616565b32305e5 broke the build on > > OpenBSD and probably other non-Linux systems. ENODATA, which is now > >

Re: Broken build on OpenBSD

2021-03-01 Thread Tom Rini
On Fri, Feb 26, 2021 at 01:01:58PM -0600, Alex G. wrote: > On 2/25/21 1:31 PM, Simon Glass wrote: > > Hi Alex, > > > > > > To the extent that it is unconventional, that reflects the decision to > > avoid adding U-Boot-specific error numbers and perhaps also to avoid > > having a different error

Re: Broken build on OpenBSD

2021-03-01 Thread Tom Rini
On Tue, Feb 23, 2021 at 08:07:21PM +0100, Mark Kettenis wrote: > Hi Simon, > > Commit c5819701a3de61e2ba2ef7ad0b616565b32305e5 broke the build on > OpenBSD and probably other non-Linux systems. ENODATA, which is now > used in fit_check_format(), isn't defined. It isn't part of POSIX[1] > and

Re: Broken build on OpenBSD

2021-02-26 Thread Alex G.
On 2/25/21 1:31 PM, Simon Glass wrote: Hi Alex, To the extent that it is unconventional, that reflects the decision to avoid adding U-Boot-specific error numbers and perhaps also to avoid having a different error number for each possible failure in U-Boot. The set of errno codes is much

Re: Broken build on OpenBSD

2021-02-25 Thread Simon Glass
Hi Alex, On Tue, 23 Feb 2021 at 17:23, Alex G. wrote: > > On 2/23/21 3:18 PM, Simon Glass wrote: > > Hi Alex, > > > > On Tue, 23 Feb 2021 at 14:48, Alex G. wrote: > >> > >> On 2/23/21 1:07 PM, Mark Kettenis wrote: > >>> Hi Simon, > >>> > >>> Commit c5819701a3de61e2ba2ef7ad0b616565b32305e5 broke

Re: Broken build on OpenBSD

2021-02-23 Thread Alex G.
On 2/23/21 3:18 PM, Simon Glass wrote: Hi Alex, On Tue, 23 Feb 2021 at 14:48, Alex G. wrote: On 2/23/21 1:07 PM, Mark Kettenis wrote: Hi Simon, Commit c5819701a3de61e2ba2ef7ad0b616565b32305e5 broke the build on OpenBSD and probably other non-Linux systems. ENODATA, which is now used in

Re: Broken build on OpenBSD

2021-02-23 Thread Tom Rini
On Tue, Feb 23, 2021 at 04:19:35PM -0500, Simon Glass wrote: > +Tom Rini > > Hi Mark, > > On Tue, 23 Feb 2021 at 14:07, Mark Kettenis wrote: > > > > Hi Simon, > > > > Commit c5819701a3de61e2ba2ef7ad0b616565b32305e5 broke the build on > > OpenBSD and probably other non-Linux systems. ENODATA,

Re: Broken build on OpenBSD

2021-02-23 Thread Simon Glass
+Tom Rini Hi Mark, On Tue, 23 Feb 2021 at 14:07, Mark Kettenis wrote: > > Hi Simon, > > Commit c5819701a3de61e2ba2ef7ad0b616565b32305e5 broke the build on > OpenBSD and probably other non-Linux systems. ENODATA, which is now > used in fit_check_format(), isn't defined. It isn't part of

Re: Broken build on OpenBSD

2021-02-23 Thread Simon Glass
Hi Alex, On Tue, 23 Feb 2021 at 14:48, Alex G. wrote: > > On 2/23/21 1:07 PM, Mark Kettenis wrote: > > Hi Simon, > > > > Commit c5819701a3de61e2ba2ef7ad0b616565b32305e5 broke the build on > > OpenBSD and probably other non-Linux systems. ENODATA, which is now > > used in fit_check_format(),

Re: Broken build on OpenBSD

2021-02-23 Thread Alex G.
On 2/23/21 1:07 PM, Mark Kettenis wrote: Hi Simon, Commit c5819701a3de61e2ba2ef7ad0b616565b32305e5 broke the build on OpenBSD and probably other non-Linux systems. ENODATA, which is now used in fit_check_format(), isn't defined. It isn't part of POSIX[1] and generally not available on

Broken build on OpenBSD

2021-02-23 Thread Mark Kettenis
Hi Simon, Commit c5819701a3de61e2ba2ef7ad0b616565b32305e5 broke the build on OpenBSD and probably other non-Linux systems. ENODATA, which is now used in fit_check_format(), isn't defined. It isn't part of POSIX[1] and generally not available on BSD-derived systems. Could you pick another error