From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeroen Hofstee Date: Sun, 16 Jun 2013 19:17:24 +0200 Subject: [U-Boot] image: Use ENOENT instead of ENOMEDIUM for better compatibility In-Reply-To: <1371394009-21590-1-git-send-email-sjg@chromium.org> References: <1371394009-21590-1-git-send-email-sjg@chromium.org> Message-ID: <51BDF324.8010808@myspectrum.nl> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Simon, On 06/16/2013 04:46 PM, Simon Glass wrote: > This error may not be defined on some platforms such as MacOS so host > compilation will fail. Use one of the more common errors instead. > > Signed-off-by: Simon Glass > > --- > common/image-fit.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/common/image-fit.c b/common/image-fit.c > index 7bf82d3..f40f160 100644 > --- a/common/image-fit.c > +++ b/common/image-fit.c > @@ -1557,7 +1557,7 @@ int fit_image_load(bootm_headers_t *images, const char *prop_name, ulong addr, > if (fit_image_get_data(fit, noffset, &buf, &size)) { > printf("Could not find %s subimage data!\n", prop_name); > bootstage_error(bootstage_id + BOOTSTAGE_SUB_GET_DATA); > - return -ENOMEDIUM; > + return -ENOENT; > } > len = (ulong)size; > This fixes building for FreeBSD as well, thanks. Regards, Jeroen