Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [for-next 3/3] package/gcc: remove gcc 4.8
Date: Sat, 13 May 2017 19:18:41 +0200	[thread overview]
Message-ID: <cb96a34a-0b54-c1eb-1c6a-14ca2ab909cb@gmail.com> (raw)
In-Reply-To: <a6njudxk1o.ln2@ID-313208.user.individual.net>

Hi Bernd,

Le 13/05/2017 ? 18:00, Bernd Kuhls a ?crit :
> Am Sat, 13 May 2017 13:37:32 +0200 schrieb Romain Naour:
> 
>> -	select BR2_TOOLCHAIN_GCC_AT_LEAST_4_8
> 
> Hi,
> 
> lots of packages contain
> 
> 	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_8
> 
> like Kodi:
> https://git.buildroot.net/buildroot/tree/package/kodi/Config.in#n40
> 
> With this patch applied these packages can not be selected anymore 
> because you removed the option BR2_TOOLCHAIN_GCC_AT_LEAST_4_8.

I'm not removing BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 option but BR2_GCC_VERSION_4_8_X
(i.e the option for the internal toolchain).

Thanks for taking a look!

Best regards,
Romain

> 
> Regards, Bernd
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

      parent reply	other threads:[~2017-05-13 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13 11:37 [Buildroot] [for-next 1/3] package/uclibc: add upstream patch to fix build issue with gcc7 Romain Naour
2017-05-13 11:37 ` [Buildroot] [for-next 2/3] package/gcc: add support for gcc 7 Romain Naour
2017-05-20 13:55   ` [Buildroot] [for-next,2/3] " Theodore Ateba
2017-05-13 11:37 ` [Buildroot] [for-next 3/3] package/gcc: remove gcc 4.8 Romain Naour
2017-05-13 16:00   ` Bernd Kuhls
2017-05-13 16:07     ` Bernd Kuhls
2017-05-13 17:18     ` Romain Naour [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=cb96a34a-0b54-c1eb-1c6a-14ca2ab909cb@gmail.com \
    --to=romain.naour@gmail.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