On Fri, 31 May 2013 01:26:07 -0400
Nick Sabalausky SeeWebsiteToContactMe@semitwist.com wrote:
By any chance, do you happen to know offhand what this set of linker
errors could be coming from?I'm still digging, but It's kinda strange: On two different machines
(My existing live server and a fairly fresh new VM instance), I have
the same OS (Debian 6), the exact same versions of vibe.d and mysqln,
the exact same main application file, the exact same DMD, exact same
libevent (2.0-5 from squeeze-backports), and I'm using the exact same
build command. And yet it works on my live server, but gives a bunch
of linker errors in the local VM machine. Darndest thing.No need to go digging a bunch if you don't know offhand, I'm sure
there's something I've overlooked and I have very detailed notes on
how I set up my server. But I thought I'd ask just in case it was a
pattern you just happened to recognize:
Ah, figures I'd finally get it mere moments after posting that.
When first I tried to install libevent-dev on this local VM, it
blindly grabbed v1.4 because I didn't tell it to grab from debian's
backports (and hadn't configured any backports repos at all). THEN I
installed libevent-2.0-5 from backports, plus all the other
libevent-*-2.0-5 packages listed. And I was surprised that my stuff
wasn't linking.
But apparently none of those 2.0 packages had updated my libevent-dev
(and there was no libevent-dev-2 or libevent-2-dev listed, which
seems kinda weird). So even installing all of the libevent 2.0 stuff
still left libevent-dev at 1.4.
So after a:
% apt-get remove libevent-dev
% apt-get -t squeeze-backports install libevent-dev
The libevent-dev is now 2.0, and all is well.