From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: gcc-patches@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org
Subject: Re: [PATCH 4/N] The big bump
Date: Sat, 15 Aug 2009 16:04:00 -0000 [thread overview]
Message-ID: <20090815160401.GB21850@gmx.de> (raw)
In-Reply-To: <4A86CC24.409@gmail.com>
* Dave Korn wrote on Sat, Aug 15, 2009 at 04:54:28PM CEST:
> Ralf Wildenhues wrote:
> > src:
> >
> > config/ChangeLog: intl/ChangeLog: libdecnumber/ChangeLog: etc/ChangeLog:
> > sim/common/ChangeLog: sim/iq2000/ChangeLog: sim/d10v/ChangeLog:
> > sim/igen/ChangeLog: sim/m32r/ChangeLog: sim/frv/ChangeLog: sim/ChangeLog:
> > sim/h8300/ChangeLog: sim/mn10300/ChangeLog: sim/ppc/ChangeLog:
> > sim/erc32/ChangeLog: sim/arm/ChangeLog: sim/m68hc11/ChangeLog:
> > sim/lm32/ChangeLog: sim/sh64/ChangeLog: sim/v850/ChangeLog:
> > sim/cr16/ChangeLog: sim/moxie/ChangeLog: sim/m32c/ChangeLog:
> > sim/mips/ChangeLog: sim/mcore/ChangeLog: sim/testsuite/d10v-elf/ChangeLog:
> > sim/testsuite/ChangeLog: sim/testsuite/frv-elf/ChangeLog:
> > sim/testsuite/m32r-elf/ChangeLog: sim/testsuite/mips64el-elf/ChangeLog:
> > sim/sh/ChangeLog: gold/ChangeLog: gprof/ChangeLog: libiberty/ChangeLog:
> > ChangeLog: opcodes/ChangeLog: readline/examples/rlfe/ChangeLog:
> > gas/ChangeLog: ld/ChangeLog: gdb/ChangeLog: gdb/doc/ChangeLog:
> > gdb/gdbserver/ChangeLog: gdb/testsuite/ChangeLog: binutils/ChangeLog:
> > bfd/ChangeLog: bfd/doc/ChangeLog: readline/ChangeLog.gdb:
>
> Looking at the toplevel of/src, there are no changes to blt/, cgen/, cpu/,
> dejagnu/, elfcpp/, expat/, expect/, itcl/, iwidgets/, libgloss/, libgui/,
> mmalloc/, newlib/, rda/, sid/, tcl/, texinfo/, tix/, tk/, utils/ and winsup/.
That is correct.
> Are these all unaffected or are some of them liable to need updates too?
I have never ever gotten a full src tree to cleanly build with
--enable-maintainer-mode, and IIRC not even without. I've always just
worked on the git binutils-gdb mirror. The rest of the tree has IMHO
lacked lots of love at least on the build system side. If you tell me
that it is used actively, and they are generally willing to see updated
build machinery (and there is somebody to review patches to this end,
timely, too), then I would look into this task. But last time I looked
I didn't think a drift apart would make things any worse; for example,
Autoconf versions used were quite inconsistent already.
Sorry if I've misunderstood things there.
I hope there is a chance this does not need to happen in lock step.
Cheers,
Ralf
next prev parent reply other threads:[~2009-08-15 16:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 11:29 Moving to Autoconf 2.64, Automake 1.11 Ralf Wildenhues
2009-08-15 11:31 ` [PATCH 1/N] Update automake-provided files in the toplevel Ralf Wildenhues
2009-08-15 11:33 ` [PATCH 3/N] some minor fixes in sim, gold, gdb Ralf Wildenhues
2009-08-17 16:14 ` Tom Tromey
2009-08-17 16:48 ` Ian Lance Taylor
2009-08-15 11:34 ` [PATCH 4/N] The big bump Ralf Wildenhues
2009-08-15 11:49 ` Richard Guenther
2009-08-15 12:23 ` Ralf Wildenhues
2009-08-15 12:29 ` Ralf Wildenhues
2009-08-15 16:21 ` Paolo Bonzini
2009-08-17 19:39 ` fix 2.64 fopen glitch, disable option checking (was: [PATCH 4/N] The big bump) Ralf Wildenhues
2009-08-17 19:57 ` fix 2.64 fopen glitch, disable option checking Paolo Bonzini
2009-08-15 14:41 ` [PATCH 4/N] The big bump Dave Korn
2009-08-15 16:04 ` Ralf Wildenhues [this message]
2009-08-15 16:36 ` Dave Korn
2009-08-15 16:26 ` Joseph S. Myers
2009-08-17 10:20 ` Nick Clifton
2009-08-23 12:30 ` Andreas Schwab
2009-08-15 11:34 ` Moving to Autoconf 2.64, Automake 1.11 Gerald Pfeifer
2009-08-16 9:49 ` Do not point to sources.redhat.com for autotools tarballs (was: Moving to Autoconf 2.64, Automake 1.11) Ralf Wildenhues
2009-08-16 17:06 ` Eli Zaretskii
2009-08-15 11:35 ` [PATCH 5/N] post-update cleanups Ralf Wildenhues
2009-08-15 16:58 ` Paolo Bonzini
2009-08-15 15:31 ` Moving to Autoconf 2.64, Automake 1.11 Joseph S. Myers
2009-08-15 16:07 ` Ralf Wildenhues
2009-08-16 11:48 ` install-{html,pdf} (was: Moving to Autoconf 2.64, Automake 1.11) Ralf Wildenhues
2009-08-17 11:14 ` install-{html,pdf} Paolo Bonzini
2009-08-17 10:34 ` install-{html,pdf} Paolo Bonzini
2009-08-15 18:04 ` Moving to Autoconf 2.64, Automake 1.11 Paolo Bonzini
2009-08-15 23:07 ` Ralf Wildenhues
[not found] ` <20090815230654.GA22525__27948.5272862532$1250377656$gmane$org@gmx.de>
2009-08-17 15:57 ` Tom Tromey
2009-08-17 18:18 ` Andreas Schwab
[not found] ` <20090815113449.GE20172__4676.41973305053$1250336143$gmane$org@gmx.de>
2009-08-17 16:17 ` [PATCH 5/N] post-update cleanups Tom Tromey
2009-08-23 10:12 ` Moving to Autoconf 2.64, Automake 1.11 Ralf Wildenhues
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=20090815160401.GB21850@gmx.de \
--to=ralf.wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
/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