From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: gdb/common/Makefile calling aclocal & autoconf...
Date: Mon, 07 Mar 2011 05:12:00 -0000 [thread overview]
Message-ID: <20110307044838.GO30306@adacore.com> (raw)
In-Reply-To: <201103061004.p26A476B018601@glazunov.sibelius.xs4all.nl>
Yao:
> The continued streem of issues with having a configure in the common/
> directory makes me convinced that Ppedro is right and we should go
> back to explicitly list things in the gdb and gdbserver Makefiles.
I think Mark are right. We are probably on the second or third "one
last push" to make things work, and we're still not done. I'm really
sorry, but we have 3 Global Maintainers (Mark, Pedro, myself) who
think that this is the wrong way to go. We tried to perservere in
this direction despite our reservations, but it's still not working.
We've learnt a lot in the process, but I think it's time to head
in the other direction (no configure & make in common/).
Anyone strongly opposed to that move, please speak up now.
It's important, IMO, to do that soon, because we're not guarantied
that we will make everything work instantly either. I will see if
I can produce some patches for review within a day or two (anyone
wanting to take care of that can, of course!).
--
Joel
next prev parent reply other threads:[~2011-03-07 4:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 10:59 Joel Brobecker
2011-03-06 7:19 ` Joel Brobecker
2011-03-06 7:45 ` Joel Brobecker
2011-03-06 10:04 ` Jan Kratochvil
2011-03-07 4:39 ` Build regression: " Jan Kratochvil
2011-03-06 11:55 ` Mark Kettenis
2011-03-07 5:12 ` Joel Brobecker [this message]
2011-03-07 5:24 ` Jan Kratochvil
2011-03-07 10:00 ` Joel Brobecker
2011-03-07 7:06 ` Yao Qi
2011-03-07 9:51 ` Joel Brobecker
2011-03-08 9:54 ` Jan Kratochvil
2011-03-08 11:12 ` Yao Qi
2011-03-08 18:24 ` Jan Kratochvil
2011-03-08 18:51 ` Mark Kettenis
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=20110307044838.GO30306@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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