datetime fails with undefined reference

[Jonathan M Davis]

On Monday 21 February 2011 08:40:38 Kai Meyer wrote:
> == Quote from Jonathan M Davis (jmdavisProg at gmx.com)'s article
> 
> > On Friday, February 18, 2011 16:27:23 Russel Winder wrote:
> > > As noted in my earlier email on the other list, I too got this problem.
> > > Fromn what I can tell 1.066 and 2.051 have dmd.conf files but there is
> > > no such thing in the 1.067 and 2.052 distributions.  So the "out of the
> > > box" configuration does seem to be "broken".
> > 
> > And as I said in my response to your other message, the proper dmd.conf
> > file _is_ in the distributed zip file. So, unless you're dealing with
> > the deb or rpm, and they're broken, and I don't know why you wouldn't be
> > seeing a new dmd.conf with the 2.052 release. But I don't know what the
> > state of the rpm or deb is. I just always use the zip file, which is
> > very simple.
> > - Jonathan M Davis
> 
> Ok, I can fix the dmd.conf. Who does manage the RPM packaging? And how can
> I get a hold of them?

I'm not sure who deals with the RPM stuff (though looking at the download on the 
site, the rpm hasn't been updated 2.052 - it's still on 2.051). If it's broken, 
post on the "dmd 1.067 and 2.052 release" thread in D.announce, since that's 
where people are generally looking for info on the release. If you haven't 
registered with the announce list, then you can just start a thread on it in the 
main D list. That's the place that the most people will notice and where you're 
most likely to get the attention of whoever it is needs to know (which may be 
Walter, but I don't know).

However, I _would_ point out that it's extremely easy to just the zip file. I've 
never bothered with the rpm, personally. So, while the rpm should definitely 
should be fixed, if all you're really looking to do is have a working dmd, using 
the zip is likely a good option. You just download it and unzip it to wherever 
you want it (e.g. your home folder) and then add the path to the linux/bin 
folder within it (e.g. ~/dmd2/linux/bin) to your PATH variable (presumably in  
your .bashrc), and it then it'll work just fine. It'll grab phobos from the right 
place and the dmd.conf will be correct. Every time that a new version is 
released, you just replace the dmd2 folder with the newly unzipped version, and 
it works.

- Jonathan M Davis