From: Andrew Cagney <ac131313@redhat.com>
To: Nick Kelsey <nickk@ubicom.com>
Cc: gdb@sources.redhat.com, Nathanael Nerode <neroden@twcny.rr.com>,
dj@redhat.com
Subject: Re: Trunk build problems
Date: Mon, 16 Dec 2002 13:01:00 -0000 [thread overview]
Message-ID: <3DFE3F30.5060304@redhat.com> (raw)
In-Reply-To: <0bff01c2a542$c47742d0$f601a8c0@nkelseyxp>
> Hi guys,
>
> I think its time for a gripe as the trunk has been going downhill rapidly
> over the last week or so.
>
> <gripe>
>
> Things I have noticed over the last week:
>
> - Configure in src doesn't do any sub directories any more (linux or
> cygwin).
This (as I've come to learn and respect) is a long overdue feature.
Once you've got over the initial shock (it took me a week ...) it really
is much much better.
- It no longer configures directories that are not needed - huge time saver!
- It can parallize configures
> - Under cygwin, libtermcap attempts to be build (which doesn't exist). This
> causes a circular make problem as it can't change into the directory so does
> a make in src again.
Sounds like Makefile.tpl (?) needs a tweak?
> - If you do an incremental make in src it reconfigures a number of
> directories *every time* (both linux and cygwin).
One case of this - bfd - was fixed. Is this another case?
> - Readline doesn't link under cygwin.
Readline was finally updated. Again, very long overdue. If there are
problems, then please report them (hopefully with fixes).
> My snapshot from about 2 weeks ago works fine - these are all new problems.
>
> I am interested if these are known problems and under active investigation.
I suspect that they are unknown (I didn't know about them).
If you're wondering these changes are occuring now so that, hopefully,
there is plenty of time to catch problems such as you are finding before
the next GDB/binutils release.
BTW, the place to report each problem is gcc@gcc.gnu.org (cc'd
gdb-patches@).
Andrew
next prev parent reply other threads:[~2002-12-16 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 12:36 Nick Kelsey
2002-12-16 12:41 ` Daniel Jacobowitz
2002-12-16 12:59 ` Elena Zannoni
2002-12-16 13:01 ` Andrew Cagney [this message]
2002-12-16 13:18 ` DJ Delorie
2002-12-22 23:43 ` Nathanael Nerode
[not found] ` <redirect-4840171@silicondust.com>
2002-12-16 13:12 ` Nick Kelsey
2002-12-16 19:22 ` Christopher Faylor
2002-12-16 17:58 ` Christopher Faylor
2002-12-16 18:06 ` Christopher Faylor
[not found] <redirect-4840161@silicondust.com>
2002-12-18 19:21 ` Nick Kelsey
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=3DFE3F30.5060304@redhat.com \
--to=ac131313@redhat.com \
--cc=dj@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=neroden@twcny.rr.com \
--cc=nickk@ubicom.com \
/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