mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegorslists@googlemail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: Cross-compiling target tools
Date: Thu, 26 Mar 2020 17:36:55 +0100	[thread overview]
Message-ID: <CAGm1_ktcbbqfBB0wbgCCdf3d8mmPWvvt0N_4AyV_U3UAsCGOxg@mail.gmail.com> (raw)
In-Reply-To: <fe2b4025-ffac-f420-d8c0-4bdcb297b71e@pengutronix.de>

Hi Ahmad,

On Thu, Mar 26, 2020 at 5:00 PM Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>
> Hi,
>
> On 3/26/20 4:31 PM, Yegor Yefremov wrote:
> > On Thu, Mar 26, 2020 at 7:36 AM Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > With these changes I get the tools bareboxenv-target etc. cross-compiled:
> >
> > diff --git a/scripts/compiler.h b/scripts/compiler.h
> > index 0891c3bfa..74cd98074 100644
> > --- a/scripts/compiler.h
> > +++ b/scripts/compiler.h
> > @@ -113,7 +113,7 @@ typedef uint32_t __u32;
> >         (void) (&_min1 == &_min2);              \
> >         _min1 < _min2 ? _min1 : _min2; })
> >
> > -inline void *xmalloc(size_t size)
> > +void *xmalloc(size_t size)
>
> This has been static inline instead for 2 years now[1]. Please check out a current
> barebox revision.
>
> [1]: 359966df3721 ("scripts/compiler.h: inline functions in headers must be static")

You're right, I was experimenting with the old version 2018.x.

Sorry for the noise.

Yegor

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2020-03-26 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 22:13 Yegor Yefremov
2020-03-26  6:36 ` Sascha Hauer
2020-03-26 15:31   ` Yegor Yefremov
2020-03-26 16:00     ` Ahmad Fatoum
2020-03-26 16:36       ` Yegor Yefremov [this message]

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=CAGm1_ktcbbqfBB0wbgCCdf3d8mmPWvvt0N_4AyV_U3UAsCGOxg@mail.gmail.com \
    --to=yegorslists@googlemail.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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