Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: automatic dependency tracking
Date: Thu, 07 Aug 2008 20:46:00 -0000	[thread overview]
Message-ID: <20080807204456.GA18762@ins.uni-bonn.de> (raw)
In-Reply-To: <m3fxpgh9on.fsf@fleche.redhat.com>

* Tom Tromey wrote on Thu, Aug 07, 2008 at 10:06:16PM CEST:
> >>>>> "Ralf" == Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
> 
> >> FWIW I did not want to change where the build puts objects; I didn't
> >> see a particular benefit to doing this.
> 
> Ralf> It allows you to remove about 190 lines from the Makefile.
> Ralf> If you like, I can redo the patch or post a followup one, for this.
> 
> I am curious about this.  I thought old-style '.c.o' rules did not
> handle subdirectories properly.  Is that not so?  Or, what approach
> were you planning to take?

Yes, I was going to rely on '.c.o' rules.  I don't remember problems
with subdirectories in .c.o rules, other than maybeee on Solaris 2.6.
But I tend to forget the details (and GNU make works on that system), on
<http://www.gnu.org/software/autoconf/manual/html_node/Portable-Make.html>
I cannot find anything else problematic.  Maybe you are thinking of
compiler problems with "-c -o"?

Anyway, automake.in has had this encouraging note since 2003
(handle_single_transform, indentation dropped):
[...]
# If both source and object files are in a subdirectory
# (this happens when the subdir-objects option is used),
# then the inference will work.
#
# The latter case deserves a historical note.  When the
# subdir-objects option was added on 1999-04-11 it was
# thought that inferences rules would work for
# subdirectory objects too.  Later, on 1999-11-22,
# automake was changed to output explicit rules even for
# subdir-objects.  Nobody remembers why, but this occurred
# soon after the merge of the user-dep-gen-branch so it
# might be related.  In late 2003 people complained about
# the size of the generated Makefile.ins (libgcj, with
# 2200+ subdir objects was reported to have a 9MB
# Makefile), so we now rely on inference rules again.
# Maybe we'll run across the same issue as in the past,
# but at least this time we can document it.  However since
# dependency tracking has evolved it is possible that
# our old problem no longer exists.
# Using inference rules for subdir-objects has been tested
# with GNU make, Solaris make, Ultrix make, BSD make,
# HP-UX make, and OSF1 make successfully.


> I think you should put your name on the ChangeLog entry.

Fine with me.  Do you want me to re-post the patch for this?  ;-)

Cheers,
Ralf


  reply	other threads:[~2008-08-07 20:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 22:14 Tom Tromey
2008-07-30 17:53 ` Pedro Alves
2008-07-30 19:12   ` Tom Tromey
2008-07-31 18:51     ` Pedro Alves
2008-07-31 10:48 ` Andrew STUBBS
2008-07-31 12:16   ` Tom Tromey
2008-07-31 14:43   ` Tom Tromey
2008-08-02 20:34     ` Thiago Jung Bauermann
2008-08-07  5:50 ` Ralf Wildenhues
2008-08-07 13:47   ` Tom Tromey
2008-08-07 13:53     ` Daniel Jacobowitz
2008-08-07 19:17     ` Ralf Wildenhues
2008-08-07 20:07       ` Tom Tromey
2008-08-07 20:46         ` Ralf Wildenhues [this message]
2008-08-07 20:51           ` Tom Tromey
2008-08-07 20:17       ` Daniel Jacobowitz
2008-08-07 20:22         ` Tom Tromey
2008-08-07 20:46           ` Ralf Wildenhues
2008-08-07 20:49             ` Tom Tromey
2008-08-07 20:59       ` Daniel Jacobowitz
2008-08-07 22:51         ` Ralf Wildenhues
2008-08-08 14:37           ` Thiago Jung Bauermann
2008-08-08 15:18             ` Tom Tromey
2008-08-08 15:24               ` Ralf Wildenhues
2008-08-08 17:27                 ` Tom Tromey
2008-08-08 17:35               ` Daniel Jacobowitz
2008-08-07 17:09   ` Tom Tromey
2008-08-07 19:23     ` 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=20080807204456.GA18762@ins.uni-bonn.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@redhat.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