bgribble/mfp

build process has bitrotted

Closed this issue · 2 comments

Somehow the waf build-from-scratch is no longer working on my local. It looks like the setup.py script is never run during ./waf build install so no mfp or mfpgui scripts are ever installed. I'm not sure how long ago this happened because I haven't done a complete build from scratch into a fresh virtual for a while.

This is definitely new behavior, and nothing has changed in the build process. Maybe a waf version bump? But we ship the waf binary for that very reason...

The build script is raising warnings like so:

Making virtualenv relocatable
Running virtualenv with interpreter /usr/bin/python2

Can't find resource wafbuild/virtual/local/bin
Can't find resource wafbuild/virtual/local/lib
Can't find resource wafbuild/virtual/local/include
Can't find resource wafbuild/virtual/local/share
Can't find resource wafbuild/virtual/local/bin
Can't find resource wafbuild/virtual/local/lib
Can't find resource wafbuild/virtual/local/include
Can't find resource wafbuild/virtual/local/share

I thought I remembered making that local link during the virtualenv setup.

Not sure what happened, but I can't reproduce this any more. I am willing to chalk it up to a Debian package upgrade on my local (I did upgrade about 100 packages since creating this ticket).

Closing this ticket, but will reopen if this happens again.