Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 02/14] toolchain: remove CodeSourcery x86 toolchain
Date: Sun, 18 Jun 2017 11:19:23 +0200	[thread overview]
Message-ID: <20170618091923.GE2918@scaer> (raw)
In-Reply-To: <20170618091424.tefhny6rq57ytdc2@tarshish>

Baruch, All,

On 2017-06-18 12:14 +0300, Baruch Siach spake thusly:
> On Sun, Jun 18, 2017 at 11:08:33AM +0200, Yann E. MORIN wrote:
> > Baruch, All,
> > 
> > On 2017-06-16 06:32 +0300, Baruch Siach spake thusly:
> > > Since glibc 2.17, executable link command need not include the -lrt option for
> > > clock_* system calls. As a result, over time less and less software packages
> > > bother to check whether to toolchain needs -lrt. We are now at a point where
> > > maintainers refuse to add this complexity into their build system. This
> > > requires Buildroot to carry patches fixing this issue indefinitely.
> > 
> > What upstreams are refusing to fix that? Do you have references to
> > share?
> 
> See http://patchwork.ozlabs.org/patch/773384/ (swupdate).
> I put the link in the series cover. Should add it here as well?

Ah, I missed it in the cover letter. Thanks.
I don't think it is important that you repeat it here.

Regards,
Yann E. MORIN.

> baruch
> 
> > 
> > > glibc 2.17 is now 4.5 years old. There is no reason to use an older version
> > > with current software.
> > 
> > So we can now consider the cut-off at what we consider legacy is 4.5
> > years old. Fine with me.
> > 
> > > This commit removes the predefined profile for CodeSourcery x86 toolchain that
> > > is based on glibc 2.16. One may still use the custom external toolchain
> > > support in Buildroot to get this toolchain back, and deal with any build
> > > issues that this toolchain causes.
> > > 
> > > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > 
> > Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> 
> -- 
>      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 -

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2017-06-18  9:19 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  3:32 [Buildroot] [PATCH 00/14] toolchain-external: remove support for glibc before 2.17 Baruch Siach
2017-06-16  3:32 ` [Buildroot] [PATCH 01/14] docs/manual: update external toolchain advantages list Baruch Siach
2017-06-18  9:02   ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 02/14] toolchain: remove CodeSourcery x86 toolchain Baruch Siach
2017-06-18  9:08   ` Yann E. MORIN
2017-06-18  9:14     ` Baruch Siach
2017-06-18  9:19       ` Yann E. MORIN [this message]
2017-06-16  3:32 ` [Buildroot] [PATCH 03/14] toolchain: remove CodeSourcery sh toolchain Baruch Siach
2017-06-18  9:09   ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 04/14] package: remove CodeSourcery sh dependencies Baruch Siach
2017-06-18  9:12   ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 05/14] toolchain-external: update list of toolchains Baruch Siach
2017-06-18  9:21   ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 06/14] docs/manual: drop mention of removed external toolchains Baruch Siach
2017-06-18  9:23   ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 07/14] swupdate: don't link with librt Baruch Siach
2017-06-18  9:26   ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 08/14] aiccu: " Baruch Siach
2017-06-18  9:27   ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 09/14] libv4l: " Baruch Siach
2017-06-18  9:31   ` Yann E. MORIN
2017-06-18  9:34     ` Baruch Siach
2017-06-18  9:36       ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 10/14] e2fsprogs: " Baruch Siach
2017-06-18  9:33   ` Yann E. MORIN
2017-06-18 10:13     ` Baruch Siach
2017-06-18 11:55       ` Yann E. MORIN
2017-06-19 19:14         ` Baruch Siach
2017-06-16  3:32 ` [Buildroot] [PATCH 11/14] liboping: no need to check for clock_gettime Baruch Siach
2017-06-18  9:37   ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 12/14] openipmi: " Baruch Siach
2017-06-18  9:42   ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 13/14] lirc-tools: " Baruch Siach
2017-06-18  9:45   ` Yann E. MORIN
2017-06-16  3:32 ` [Buildroot] [PATCH 14/14] softether: " Baruch Siach
2017-06-18  9:47   ` Yann E. MORIN
2017-06-20 20:23 ` [Buildroot] [PATCH 00/14] toolchain-external: remove support for glibc before 2.17 Thomas Petazzoni
2017-06-22  7:57 ` Arnout Vandecappelle
2017-06-22 17:01   ` Baruch Siach
2017-06-23 21:33     ` Waldemar Brodkorb
2017-06-25  4:57       ` Baruch Siach

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=20170618091923.GE2918@scaer \
    --to=yann.morin.1998@free.fr \
    --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