From: Silas McCroskey <inkswinc@gmail.com>
To: 9front@9front.org
Subject: some mkfiles assume '.' in path env var
Date: Mon, 13 Apr 2020 19:45:24 -0700 [thread overview]
Message-ID: <CAHjwAuyPEzY90hgBuTu5q+-fN1Bn6xzpSZ-V6+AMhe9rYA3LkQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
here's hoping gmail doesn't mangle the hell outta this. Sending as an
attachment as well in case it does.
Updated for the first time in a while today and was flummoxed for a
bit before figuring this out. A bit surprised that rc doesn't just do
the right thing here, but it's easy enough to fix.
- sam-d
---
diff -r 1639f326a090 sys/src/cmd/7l/mkfile
--- a/sys/src/cmd/7l/mkfile Tue Apr 14 02:04:54 2020 +0000
+++ b/sys/src/cmd/7l/mkfile Tue Apr 14 02:36:54 2020 +0000
@@ -29,7 +29,7 @@
@ { cd ../7c; mk enam.c }
cnam.c: l.h mkcname
- rc mkcname
+ rc ./mkcname
enam.$O: ../7c/enam.c
$CC $CFLAGS ../7c/enam.c
diff -r 1639f326a090 sys/src/cmd/ql/mkfile
--- a/sys/src/cmd/ql/mkfile Tue Apr 14 02:04:54 2020 +0000
+++ b/sys/src/cmd/ql/mkfile Tue Apr 14 02:36:54 2020 +0000
@@ -26,5 +26,5 @@
enam.$O: ../qc/enam.c
$CC $CFLAGS ../qc/enam.c
cnam.c: l.h
- rc mkcname
+ rc ./mkcname
compat.$O: ../cc/compat
[-- Attachment #2: patch --]
[-- Type: application/octet-stream, Size: 605 bytes --]
diff -r 1639f326a090 sys/src/cmd/7l/mkfile
--- a/sys/src/cmd/7l/mkfile Tue Apr 14 02:04:54 2020 +0000
+++ b/sys/src/cmd/7l/mkfile Tue Apr 14 02:36:54 2020 +0000
@@ -29,7 +29,7 @@
@ { cd ../7c; mk enam.c }
cnam.c: l.h mkcname
- rc mkcname
+ rc ./mkcname
enam.$O: ../7c/enam.c
$CC $CFLAGS ../7c/enam.c
diff -r 1639f326a090 sys/src/cmd/ql/mkfile
--- a/sys/src/cmd/ql/mkfile Tue Apr 14 02:04:54 2020 +0000
+++ b/sys/src/cmd/ql/mkfile Tue Apr 14 02:36:54 2020 +0000
@@ -26,5 +26,5 @@
enam.$O: ../qc/enam.c
$CC $CFLAGS ../qc/enam.c
cnam.c: l.h
- rc mkcname
+ rc ./mkcname
compat.$O: ../cc/compat
next reply other threads:[~2020-04-14 2:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 2:45 Silas McCroskey [this message]
2020-04-18 17:08 ` [9front] " cinap_lenrek
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=CAHjwAuyPEzY90hgBuTu5q+-fN1Bn6xzpSZ-V6+AMhe9rYA3LkQ@mail.gmail.com \
--to=inkswinc@gmail.com \
--cc=9front@9front.org \
/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).