All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: gcc 4.4 is the lowest we are known to work with
Date: Thu, 09 Aug 2018 16:14:52 +0300	[thread overview]
Message-ID: <87a7pvbs1f.fsf@tkos.co.il> (raw)
In-Reply-To: <CANQCQpZv0zcAV4L_ZdRk21e22GLw5pzaTe_2JoH0kN_uC4Tumw@mail.gmail.com>

Hi Matt,

Matthew Weber writes:
> On Sun, Aug 5, 2018 at 6:46 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>>
>> gcc-2.95 is old. No, it is not old; it is antediluvian.
>>
>> The odlest gcc version we are testing against is gcc-4.4 (on Holiss'
>> autobuilder using RHEL6.5).
>>
>
> Any suggestions if we keep the minimum host compiler requirement at
> 4.4, how should I address the below build failures with "error:
> '__ATOMIC_ACQUIRE' undeclared " on the RHEL6.5 autobuilder?
> http://autobuild.buildroot.net/?reason=host-libselinux-2.7
>
> If this was a more recent compiler version issue, I'd dig into the
> package and look at up-streaming a compatibility ifdef check.

The atomic operations were introduced in gcc version 4.7:

  https://gcc.gnu.org/gcc-4.7/changes.html

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  reply	other threads:[~2018-08-09 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-05 11:46 [Buildroot] [PATCH] docs/manual: gcc 4.4 is the lowest we are known to work with Yann E. MORIN
2018-08-09 13:08 ` Matthew Weber
2018-08-09 13:14   ` Baruch Siach [this message]
2018-08-09 13:41     ` Matthew Weber
2018-08-09 17:14   ` Hollis Blanchard
2018-08-13 14:35     ` Matthew Weber

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=87a7pvbs1f.fsf@tkos.co.il \
    --to=baruch@tkos.co.il \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.