Skip to content

Commit

Permalink
GitHub #220: Update READMEs for this issue.
Browse files Browse the repository at this point in the history
  • Loading branch information
bgribble committed Oct 29, 2014
1 parent 074bfeb commit c442a2b
Show file tree
Hide file tree
Showing 3 changed files with 20 additions and 0 deletions.
9 changes: 9 additions & 0 deletions CHANGELOG
@@ -1,3 +1,12 @@
mfp v0.05.1, 2014-Oct-29

* #219: Solve wscript errors with Python 2.x

* #221: Fix LD_LIBRARY_PATH pollution

* #220: (not closed) Add notes to README.md and README.build about potential
errors on 'waf install'

mfp v0.05, 2014-Oct-28

* #134: Add -v/--verbose to log console messages to stdout
Expand Down
10 changes: 10 additions & 0 deletions README.build
Expand Up @@ -122,4 +122,14 @@ INSTALLING
The installation root defaults to /usr/local and can be modified
by passing in the --prefix argument to "./waf configure".

If you get errors on the install step to the effect of os.symlink
failing to make a link because the file already exists -- see GitHub
issue #220 and please add a comment indicating your Linux distribution
and that you are having this problem.

Note that the instances of #220 I have seen are failing at the
very tail end of the install process, and are trying to install
files that are already there... which means that you can probably
ignore this error. Try activating the virtualenv and running
mfp. If it launches, you are good to go.

1 change: 1 addition & 0 deletions README.md
Expand Up @@ -70,6 +70,7 @@ Ticket | Description
#217 | MFP must be stopped with `kill -9` in (hopefully rare) error conditions. Workaround: ^Z to stop the process from the shell, then `kill -9 %1`
#204 | Logging is broken when loaded as LV2 plugin 98 | Selecting connections with click or box doesn't work well. Workaround: Zoom in and click right on the line.
#212 | Rendering of smooth curves on XY plot shows gaps
#220 | 'waf install' can give error messages. Workaround: See the bottom of README.build; possibly no action is required.

See the tickets in GitHub for detail on what I know about these problems, and for
other potential workarounds.
Expand Down

0 comments on commit c442a2b

Please sign in to comment.