cannot allocate memory in static TLS block
I have a ubuntu 12.04 spin in which I am running dmd hello.d -shared -defaultlib=libphobos2.so -ofhello.so on an empty hello.d. attempting to use it (python) results in Traceback (most recent call last): File "test.py", line 1, in import hello ImportError: /usr/lib/i386-linux-gnu/libphobos2.so.0.65: cannot allocate memory in static TLS block anyone else seeing this? dmd 2.065, deb package from dlang.org.
Re: Fedora DMD package
On Friday, 6 June 2014 at 15:24:20 UTC, Russel Winder via Digitalmars-d wrote: OK, I can perhaps see why glibc-devel, but the rest? And why i686 packages on an x86_64 machine? Thanks. to support -m32, probably
pyd - continuous integration
So pyd is at the point where it really needs some sort of test suite runner. It's kind of complicated since I need to test against * multiple versions of dmd/ldc/gdc * multiple versions of python (2.4 - 3.4, but I'm thinking of dropping 2.4 and 2.5 this year) * redhat, ubuntu, osx, windows, etc Does anyone have any suggestions on how or where to set this up? I had a peek at atlassian bamboo, but it looks like it only plays with ec2, which I don't know anything about.
Re: pyd - continuous integration
On Tuesday, 10 June 2014 at 14:39:25 UTC, Atila Neves wrote: If you can spare the time / HW resources, I'd probably go with Vagrant and Buildbot, but then again I would since I'm familiar with both. Atila I stumbled on vagrant a few months ago but haven't had a chance to play with it yet. I take it you need a pretty beefy box to use it? Another thing I was envisioning is a web page that shows test results for each combination so that it is easy for a casual user to determine pyd's status. Does buildbot have this sort of thing?
Re: readln for tango with d2?
On Monday, 23 June 2014 at 10:52:32 UTC, seany wrote: Doese tango come with a readline fucntion for d2? from this site, i was unable to find anything in my search : http://siegelord.github.io/Tango-D2/ tango.io.Console, maybe?
Re: Future(s) for D.
On 06/20/2015 07:00 AM, Etienne wrote: On Saturday, 20 June 2015 at 13:33:34 UTC, Dragos Carp wrote: On Saturday, 20 June 2015 at 12:35:11 UTC, weaselcat wrote: I recently read this facebook post on their future implementation in their Folly library. https://code.facebook.com/posts/1661982097368498 This made me slightly envious. Thoughts on a D implementation? Even if the callbacks are sequentially listed, the "callback hell" is still there. A better solution is to use fibers. You can take a look at a fibers[1] and tasks[2] implementation in asynchronous library[3]. [1] - https://github.com/dcarp/asynchronous/blob/master/src/asynchronous/futures.d [2] - https://github.com/dcarp/asynchronous/blob/master/src/asynchronous/tasks.d [3] - http://code.dlang.org/packages/asynchronous Yep, looks like we already have better. I don't understand how D hasn't fully picked up in Web Dev at this point. Are they expecting an e-commerce/blogging/cms platform to go with it? A while back I was bored and curious to see how vibe would fare in the web framework benchmarks (http://www.techempower.com/benchmarks/) so I started adding vibe to it (https://github.com/ariovistus/FrameworkBenchmarks). Chose to go with ddb. Postgresql+asynchronous, sounds great. It didn't compile with the latest dmd at the time. So I fixed it up, made a PR, and it worked fine. It looked like I was getting results close to netty (in json serialization) without much effort, but ultimately, I set it aside to wait for my PR to be merged. what is the deal with ddb, anyways? Is it dead?
