Marcin Cieślak

```` > node -p process.config { target_defaults: { cflags: [], default_configuration: 'Release', defines: [], include_dirs: [ '/usr/local/include', '/usr/local/include', '/usr/local/include' ], libraries: [ '-lz', '-L/usr/local/lib', '-luv', '-L/usr/local/lib', '-lcares', '-L/usr/local/lib', '-licui18n', '-licuuc',...

@bnoordhuis I need solution to this problem quite urgently, do you think this is a way to go forward? Can you (or anyone) think of better alternatives? (I agree that...

Yes, definitely, this is the #1 reason why plain compilation of binary extensions fails on FreeBSD - `uv.h` cannot be found.

> At least if the OpenSSL subdirectory was in a separate directory (e.g. `include/_openssl`, which should never interfere with a `#include `), addons could conditionally exclude that directory, which would...

I wonder if there is anything a client can do? This issue looks like a number of server-side issues. (I'd love to see a public bug tracker for these)

You don't say if XXX source ports are the same or different ones? Is the `ESTABLISHED` connection still transferring data and your concern is only about `CLOSE_WAIT` ones?

@kpcyrd can you try the newest version? #277 should be fixed there...

I have submitted the necessary changes to @ppenzin: [ snip ] Well, it doesn't seem to be that simple. I don't know why cmake is used in such a relatively...

I'd say this is pretty interesting. Wish libsass had a possibility to do this before running everything, i.e just by parsing the files.

I don't think we should add this to such a minimal wrapper... maybe there could be another program that wraps the execution of sassc.exe and prints it? timer.exe sassc.exe