deps.sh meet compile error in Ubuntu 14.10 about proxygen

[bugok]

@xiaomi-tc: I think this might be related to unsynced code. Can you please try again? I pushed our latest branch yesterday.

[xiaomi-tc]

I had a retry , but the same error

libtool: compile: g++ -DHAVE_CONFIG_H -I./.. -pthread -I/usr/include -std=gnu++0x -g -O2 -MT io/async/AsyncSSLSocket.lo -MD -MP -MF io/async/.deps/AsyncSSLSocket.Tpo -c io/async/AsyncSSLSocket.cpp -o io/async/AsyncSSLSocket.o >/dev/null 2>&1

io/async/EventBase.cpp: In member function 'virtual void folly::EventBase::FunctionRunner::messageAvailable(std::pair<void (*)(void*), void*>&&)':
io/async/EventBase.cpp:77:46: error: 'event_base_loopbreak'  was not declared in this scope
     event_base_loopbreak(getEventBase()->evb_);
                                              ^

io/async/EventBase.cpp: In constructor 'folly::EventBase::EventBase(bool)':
io/async/EventBase.cpp:170:10: error: invalid conversion from 'void_' to 'event_base_' [-fpermissive]
evb_ = (ev.ev_base) ? event_base_new() : event_init();
^
io/async/EventBase.cpp: In member function 'void folly::EventBase::terminateLoopSoon()':
io/async/EventBase.cpp:477:28: error: 'event_base_loopbreak' was not declared in this scope
event_base_loopbreak(evb_);

[QiMata]

I am getting the same thing with Ubuntu 14.04. Even with the repo update.

Full error:

In file included from HTTPConnector.cpp:15:0:
../../../proxygen/lib/http/session/HTTPTransaction.h: In member function 'void proxygen::HTTPTransaction::refreshTimeout()':
../../../proxygen/lib/http/session/HTTPTransaction.h:960:55: error: no matching function for call to 'folly::HHWheelTimer::scheduleTimeout(proxygen::HTTPTransaction* const)'
transactionIdleTimeouts_->scheduleTimeout(this);
^
../../../proxygen/lib/http/session/HTTPTransaction.h:960:55: note: candidate is:
In file included from ../../../proxygen/lib/http/HTTPConnector.h:14:0,
from HTTPConnector.cpp:10:
/usr/local/include/folly/io/async/HHWheelTimer.h:192:8: note: void folly::HHWheelTimer::scheduleTimeout(folly::HHWheelTimer::Callback_, std::chrono::milliseconds)
void scheduleTimeout(Callback_ callback,
^
/usr/local/include/folly/io/async/HHWheelTimer.h:192:8: note: candidate expects 2 arguments, 1 provided

My commands leading up to this are, fresh install of 14.04 on Parallels.
sudo apt-get update
sudo apt-get install git
cd ./Documents
sudo clone https://github.com/facebook/proxygen.git
cd ./proxygen/proxygen
sudo ./deps.sh && ./reinstall.sh

[afrind]

What version of libevent do you have on your system?

From: Jared Rhodes <[email protected]mailto:[email protected]>
Reply-To: facebook/proxygen <[email protected]mailto:[email protected]>
Date: Tuesday, September 22, 2015 at 8:26 AM
To: facebook/proxygen <[email protected]mailto:[email protected]>
Subject: Re: [proxygen] deps.sh meet compile error in Ubuntu 14.10 (#62)

I am getting the same thing with Ubuntu 14.04. Even with the update.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/62#issuecomment-142323176.

[QiMata]

thinking this is what you want
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii libevent-2.0-5 2.0.21-stabl amd64 Asynchronous event notification l
ii libevent-core- 2.0.21-stabl amd64 Asynchronous event notification l
ii libevent-dev 2.0.21-stabl amd64 Asynchronous event notification l
ii libevent-extra 2.0.21-stabl amd64 Asynchronous event notification l
ii libevent-opens 2.0.21-stabl amd64 Asynchronous event notification l
ii libevent-pthre 2.0.21-stabl amd64 Asynchronous event notification l

[afrind]

@QiMata : your error is actually different (nothing about event_base_loopbreak). Looks like the folly rev is behind where it should be. Try setting it to v0.55.0. I will update it when I push this week, not sure how it didn't get updated with any previous push in the last month.

[QiMata]

@afrind It works but you also have to update the wangle version to 0.13.0 as well

[afrind]

@QiMata : I just pushed, so HEAD should be good now. I also updated our push procedure so it shouldn't get missed again. Feel free to reopen if it's not working.