It worked. Thanks to you, Murphy, its installed. Phew :) On Wed, Jul 11, 2012 at 10:28 PM, Murphy McCauley <[email protected] > wrote:
> Well at least you're continuing to get further and further. :) > > I guess you're using GCC 4.7? > > Try reconfiguring like this: > CXXFLAGS=-fpermissive ../configure > > Then run make again. > > This fix won't work for future GCC versions, but I am not likely to ever > do the real fix, since I don't really work on NOX-Classic anymore. If > someone else wants to do it, feel free to send a patch to the list. > > -- Murphy > > On Jul 11, 2012, at 9:34 AM, Neha Jatav wrote: > > This time make gave me this error: > /usr/include/boost/smart_ptr/intrusive_ptr.hpp:91:23: error: > 'intrusive_ptr_add_ref' was not declared in this scope, and no declarations > were found by argument-dependent lookup at the point of instantiation > [-fpermissive] > PFA the make output > > On Wed, Jul 11, 2012 at 8:51 PM, Murphy McCauley < > [email protected]> wrote: > >> If you don't have it anymore, I am worried about the state of your >> repository. You could try getting it again using git checkout, but I'd >> suggest you start from scratch since something has apparently gone wrong. >> >> git clone git://noxrepo.org/nox >> Replace the ax_boost_base.m4 file. >> ./boot.sh >> mkdir build && cd build >> ../configure >> make >> >> -- Murphy >> >> On Jul 11, 2012, at 7:24 AM, Neha Jatav wrote: >> >> Dear Murphy, >> >> Earlier when I did a locate pyopenflow.py, I saw the following output: >> /home/neha/nox/src/nox/lib/pyopenflow.py >> However, after seeing your mail when I did ls in that location, I didn't >> find it. I couldn't find it on the internet either. Could you please attach >> it and send it to me? >> >> Regards, >> Neha >> >> On Wed, Jul 11, 2012 at 5:18 PM, Murphy McCauley < >> [email protected]> wrote: >> >>> 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> >>> >>> >>> >> >> > <make_output.txt> > > >
