search for: sneek

For those following the portable CVS tree.. I'd suggest holding off for a day or so unless you really want to get dirty. I just commited 32 patches from the OpenBSD tree, but have not worked out all the issues (due to Linux brain damage <sigh..Faster OpenBSD gets SMP..the happer I'll be>). The two things that need to be finished integrated in the configure.in is KRB5 and

...udo make install ? Just this past week I've rolled my own builds using the Tiger XCode-2.2 set to specify the 10.4u SDK and gcc-4. I always begin with the project's latest original tar.gz files, sometimes needing to get updates via CVS/SVN (whatever each project uses). When I am stuck, I sneek into Fink's unstable base/dists CVS to see how they compiled it. ;) But lately it seems most projects have incorporated whatever patches were required to make work on OSX, which means Fink and DarwinPorts themselves are probably way back-level. Of these Xiph projects, I've just looked at...

hello guys, i want to use facebook api for my app any body have any idea.... -- Arun Agrawal --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send

Hi! I am resending the following message about problems with utmp handling. * In the meantime I had some request in private mail from people asking whether I have new information. * The problem is still persistant in 2.9p2. * My own new investigations show, that the problem only appears with protocol 2, not with protocol 1, I therefore only started to note it when protocol 2 became the

hello everyone. i guess this has been asked before, but haven't found it in the faq. i have the following issue... it is not uncommon nowadays to have desktops with filesystems in the order of 500gb/1tb. now, my kubuntu (but other distros do the same) forces a fsck on ext3 every so often, no matter what. in the past it wasn't a big issue. but with sizes increasing so much, users are

For future reference, it looks like we should avoid DONT_RESOLVE_DLL_REFERENCES in any extensions. http://weblogs.asp.net/oldnewthing/archive/2005/02/14/372266.aspx Regards, Dan