public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: dependency generation changes
Date: Fri, 02 May 2003 04:27:00 -0000	[thread overview]
Message-ID: <3EB1F34D.7010305@redhat.com> (raw)
In-Reply-To: <200305020221.h422LVb08611@magilla.sf.frob.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This new method has a problem with -jN, N > 1.  The stamp.oST files are
sometimes not created before needed in another goal.

- -- 
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+sfNN2ijCOnn/RHQRAkdSAJ0Yr6t6OthNivONp+PYM1BlNThLwQCcDjFx
nrXtnspuMBXZ1CXK/QWgfyQ=
=Hp6d
-----END PGP SIGNATURE-----

  reply	other threads:[~2003-05-02  4:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  2:21 Roland McGrath
2003-05-02  4:27 ` Ulrich Drepper [this message]
2003-05-02  7:21   ` Roland McGrath

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=3EB1F34D.7010305@redhat.com \
    --to=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).