From: Russ Cox <russcox@gmail.com>
To: lucio@proxima.alt.za,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] /386/lib/libmp.a
Date: Thu, 27 May 2004 08:13:27 -0500 [thread overview]
Message-ID: <ee9e417a04052706136513831@mail.gmail.com> (raw)
In-Reply-To: <eda6dd2bf9b8042d1694a1e3be320ace@proxima.alt.za>
> I have a feeling that a mkfile rule causes this file to be updated
> unnecessarily. Often, the only change on sources turns out to be
> 386/lib/libmp.a. I have yet to see any of the contributing object or
> source files undergoing any changes.
This is definitely a bug, but I'm not sure how it's happening.
Sometimes libmp.a gets built with the C versions of the assembly
functions instead of the assembly.
Russ
next prev parent reply other threads:[~2004-05-27 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 8:13 lucio
2004-05-27 13:13 ` Russ Cox [this message]
2004-05-27 14:21 ` Russ Cox
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=ee9e417a04052706136513831@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=lucio@proxima.alt.za \
/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 NNTP newsgroup(s).