From: "Henry Baragar" <henry.baragar@instantiated.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: mk(file) question
Date: Wed, 5 Jun 2002 10:59:45 -0400 [thread overview]
Message-ID: <20020605145945.13219.qmail@a.mx.instantiated.ca> (raw)
In-Reply-To: <de39561d8dadb16d6dd71ac2e39216fe@plan9.bell-labs.com>
I thought the Plan 9 way was:
bind -b /usr/pac/include /sys/include
Russ Cox writes:
> you don't tell mk, you tell the compiler.
> the default mkfiles compile with
>
> $CC $CFLAGS $stem.c
>
> so you can add
>
> CFLAGS=$CFLAGS -I/usr/pac/include
>
> and similarly
>
> LDFLAGS=-L/usr/pac/$objtype/lib
>
> look at /sys/src/cmd/mkone for the rules
> being used. there's no builtin magic.
>
next prev parent reply other threads:[~2002-06-05 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 14:40 [9fans] " Russ Cox
2002-06-05 14:59 ` Henry Baragar [this message]
2002-06-10 10:03 ` peter a. cejchan
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=20020605145945.13219.qmail@a.mx.instantiated.ca \
--to=henry.baragar@instantiated.ca \
--cc=9fans@cse.psu.edu \
/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).