From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] host-m4: fix build when -std=gnu99 and inline functions are used
Date: Fri, 26 Feb 2016 09:40:51 +0000 [thread overview]
Message-ID: <1456479651.28645.18.camel@synopsys.com> (raw)
In-Reply-To: <20160226091921.6e367255@free-electrons.com>
Hi Thomas,
On Fri, 2016-02-26 at 09:19 +0100, Thomas Petazzoni wrote:
> Hello,
>
> On Fri, 26 Feb 2016 07:20:24 +0000, Alexey Brodkin wrote:
>
> > > ?I think you can basically say your host toolchain is broken: it fails to
> > > compile valid programs, because glibc doesn't satisfy the -std=gnu99 option.
> >
> > That's very true. But it looks like on RedHat/CentOS 5.x (which are still
> > in use here and there) discussed problem exists.
> >
> > Given default gcc in RHEL 5 is 4.1 (though 3.4 and 4.4 are available via
> > compat-gcc-34 and gcc44 correspondingly) ad it fails to compile host tar and m4
> > in current Buildroot I would still look for a permanent solution in vanilla
> > Buildroot instead of work-around on per machine basis.
>
> With the default gcc 4.1 used in RHEL5, I would assume that glibc 2.5
> works fine and that you can use Buildroot with no problem. Have you
> tried building Buildroot with the default gcc 4.1 ?
>
> What Arnout calls a broken toolchain is your combination of gcc 4.9 and
> glibc 2.5.
Ok so finally I made one good experiment - built Buildroot from scratch
with gcc 4.1 and you know what - it was built perfectly fine.
So I think what we first did was a real misuse - I hope lesson will be
learned - it's risky to use shiny new stuff on ages old machines :)
I.e. both patches could be dropped now and I'll make sure people
uses correct combo of tools on our farm machines.
And sorry for that noise!
-Alexey
prev parent reply other threads:[~2016-02-26 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 11:37 [Buildroot] [PATCH 0/2] fix-build-when-std-gnu99-and-inline-functions-are-used Lada Trimasova
2016-02-25 11:37 ` [Buildroot] [PATCH 1/2] host-tar: fix build when -std=gnu99 and inline functions are used Lada Trimasova
2016-02-25 11:37 ` [Buildroot] [PATCH 2/2] host-m4: " Lada Trimasova
2016-02-25 12:54 ` Thomas Petazzoni
2016-02-25 12:58 ` Lada Trimasova
2016-02-25 13:26 ` Thomas Petazzoni
2016-02-25 15:33 ` Alexey Brodkin
2016-02-25 22:13 ` Arnout Vandecappelle
2016-02-26 7:20 ` Alexey Brodkin
2016-02-26 8:19 ` Thomas Petazzoni
2016-02-26 9:40 ` Alexey Brodkin [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=1456479651.28645.18.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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