Google Git
Sign in
plan9port / plan9 / 44eb2088299f10d45a1b3950285c3314217e0f44
commit44eb2088299f10d45a1b3950285c3314217e0f44[log] [tgz]
authorRuss Cox <rsc@swtch.com>Tue Aug 25 15:59:43 2015 -0400
committerRuss Cox <rsc@swtch.com>Thu Aug 27 00:36:40 2015 +0000
tree6a934a03efa3a62d299f64c6cbe4bbaf9869f12c
parent775cb933ecea6361717ef1def27b5d9e90c385fd [diff]
mk: avoid infinite loop when targets are repeated

Fixes "mk -f /tmp/x.mk y x" or "mk -f /tmp/x.mk" where /tmp/x.mk is:

x y x: f
	echo hi

Change-Id: I7fa87dc4750c04fdba010b990c190722b432b333
Reviewed-on: https://plan9port-review.googlesource.com/1361
Reviewed-by: Russ Cox <rsc@swtch.com>
2 files changed
tree: 6a934a03efa3a62d299f64c6cbe4bbaf9869f12c
  1. acid/
  2. bin/
  3. dict/
  4. dist/
  5. face/
  6. font/
  7. include/
  8. lib/
  9. log/
  10. lp/
  11. mac/
  12. mail/
  13. man/
  14. ndb/
  15. news/
  16. plumb/
  17. postscript/
  18. proto/
  19. sky/
  20. src/
  21. tmac/
  22. troff/
  23. unix/
  24. .gitignore
  25. CHANGES
  26. configure
  27. CONTRIBUTING.md
  28. CONTRIBUTORS
  29. INSTALL
  30. install.txt
  31. LICENSE
  32. Makefile
  33. rcmain
  34. README.md
  35. TODO
README.md

This is a port of many Plan 9 libraries and programs to Unix.

Installation

To install, run ./INSTALL. It builds mk and then uses mk to run the rest of the installation.

For more details, see install(1), at install.txt in this directory and at http://swtch.com/plan9port/man/man1/install.html.

Documentation

See http://swtch.com/plan9port/man/ for more documentation. (Documentation is also in this tree, but you need to run a successful install first. After that, “9 man 1 intro”.)

Intro(1) contains a list of man pages that describe new features or differences from Plan 9.

Helping out

If you'd like to help out, great! The TODO file contains a small list.

If you port this code to other architectures, please share your changes so others can benefit.

Please use codereview(1) to prepare patches.

Git

You can use Git to keep your local copy up-to-date as we make changes and fix bugs. See the git(1) man page here (“9 man git”) for details on using Git.

Contact