On Sat, 2014-07-26 13:31:42 -0400, Hans-Peter Nilsson wrote:
> On Fri, 25 Jul 2014, Hans-Peter Nilsson wrote:
> > Anyway, on to the point of this message: by the quoted list it
> > seems you have a local host called pluto using 4.9.1 as the host
> > gcc for some build; does config-list.mk work for
On Fri, 25 Jul 2014, Hans-Peter Nilsson wrote:
> Anyway, on to the point of this message: by the quoted list it
> seems you have a local host called pluto using 4.9.1 as the host
> gcc for some build; does config-list.mk work for that?
Never mind, I found a 4.9.1 installation on gcc110 and the
ans
On Fri, 25 Jul 2014, Jan-Benedict Glaw wrote:
> On Thu, 2014-07-24 16:30:13 -0400, Hans-Peter Nilsson
> wrote:
> > On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote:
> > > On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson
> > > wrote:
> > > > Jan-Benedict, which host gcc version do you use when
On Thu, 2014-07-24 16:30:13 -0400, Hans-Peter Nilsson wrote:
> On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote:
> > On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson
> > wrote:
> > > Jan-Benedict, which host gcc version do you use when getting
> > > most targets to build with config-list.mk? M
On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote:
> On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson
> wrote:
> > Jan-Benedict, which host gcc version do you use when getting
> > most targets to build with config-list.mk? Maybe we can just
> > set the initial version to that instead of 4.4.4.
>
On Tue, 22 Jul 2014, Mike Stump wrote:
> Then I’m shadow boxing. I assumed that people wanted to turn it on by
> default. I’m all for that, I think it is a good idea and a fine
> direction. :-) The only limitation is whitelisting exactly when it
> pops on and preflighting those at least onc
On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson wrote:
> In the name of "dealing with the fallout": with the patch below
> (don't forget to re-generate configure) I get build errors in
> generic code r212915 for *both* x86_64 "gcc version 4.7.2
> 20120921 (Red Hat 4.7.2-2) (GCC)" for mmix-kn
On Jul 22, 2014, at 6:22 PM, Hans-Peter Nilsson wrote:
> Note that I didn't actually ask for approval.
Then I’m shadow boxing. I assumed that people wanted to turn it on by default.
I’m all for that, I think it is a good idea and a fine direction. :-) The
only limitation is whitelisting exa
On Tue, 22 Jul 2014, Mike Stump wrote:
> On Jul 22, 2014, at 1:40 PM, Hans-Peter Nilsson wrote:
> >
> > *Developers* (or rather, people cross-building non-released gcc
> > source in their usual setup) don't use the fairly old or even
> > broken host gcc versions that can be expected in use in the
On Jul 22, 2014, at 1:40 PM, Hans-Peter Nilsson wrote:
>
> *Developers* (or rather, people cross-building non-released gcc
> source in their usual setup) don't use the fairly old or even
> broken host gcc versions that can be expected in use in the
> general public (well, the users that still wan
Hans-Peter Nilsson writes:
> gcc:
> * configure.ac: For cross-builds of non-releases with gcc 4.4.4
> and newer, enable -Werror. Provide per-target exceptions, and do
> except vax-*.
This will break when a new printf format is added.
Andreas.
--
Andreas Schwab, sch...@linux
11 matches
Mail list logo
