I'd suggest you try deleting your build directory and starting from there. Make a new build directory, run configure, then make.
If it still complains, check that pyopenflow.py is in src/nox/lib and that it's symlinked in build/src/nox/lib. And let me know what OS you're using. -- Murphy On Jul 11, 2012, at 4:40 AM, Neha Jatav wrote: > Yeah, I didn't re-run ./boot.sh > ./configure worked after that :) > However, make ran into the following error: > make[6]: *** No rule to make target `pyopenflow.py', needed by `all'. Stop. > The output of make is attached with this email. > > On Wed, Jul 11, 2012 at 3:41 PM, Murphy McCauley <[email protected]> > wrote: > I guess I didn't say this before, but after replacing ax_boost_base.m4, you > need to re-run ./boot.sh. Did you do that? > > Also, you ARE sure you have the relevant boost development packages > installed, right? I think you need at least boost filesystem, boost system, > boost unit test, and possibly some others. On Ubuntu and Debian I usually > just install the metapackage which installs all of the boost development > stuff (libboost-all-dev). > > If you do want to try specifying the paths manually... you can try any of the > --with-boost... options that you can see when you do configure --help. I'd > start by figuring out where your boost libraries are installed (/usr/lib64?) > and manually specifying that with --with-boost=/usr/lib64 and see if that > does any good. > > -- Murphy > > On Jul 11, 2012, at 2:52 AM, Neha Jatav wrote: > >> Thanks, Murphy. The attached version didn't work. Can you please specify >> which variables do I need to set? >> >> On Wed, Jul 11, 2012 at 1:02 AM, Murphy McCauley <[email protected]> >> wrote: >> I think it's looking in lib instead of lib64. >> >> Can you try replacing config/ax_boost_base.m4 with the attached version? >> >> If this doesn't work, you might try manually setting the boost paths on the >> ./configure commandline. >> >> -- Murphy >> >> >> On Jul 10, 2012, at 7:07 AM, Neha Jatav wrote: >> >> > I have done a checkout from the destiny branch. I am facing the same >> > problem. Please find config.log & configure output attached with this >> > e-mail. >> > >> > -Neha >> > <configure_output.txt><config.log> >> >> >> > > > <make_output.txt>
