Joe Ferner

Do you have a particular dependency that has this problem?

Are you doing something like this in your `settings.xml` or is it more complex? ``` xml ... planetmirror.com PlanetMirror Australia http://downloads.planetmirror.com/pub/maven2 central ... ```

Sorry, I haven't had a chance to look into this issue.

Unfortunately MOSFET pin numbering is not standard. Here are a couple examples. https://cdn.sparkfun.com/assets/learn_tutorials/4/2/3/5lp01sp-legend.png https://is.alicdn.com/img/pb/192/774/382/382774192_169.jpg That's why I created MOSFET-N-123.lib and MOSFET-N-134.lib to help out with this. Moving forward with this...

I've updated the README with some troubleshooting tips https://github.com/joeferner/node-portaudio/commit/413e7a836401418335f1d642ad7011ad51755da3 Let me know if those help.

Try running ``` sudo ldconfig ``` If that doesn't help try ``` sudo updatedb locate libportaudio.so ``` Should be in /usr/lib/x86_64-linux-gnu/ or something like that. Then run... ``` nm -D...

You can try running ``` ldd ./build/Release/portAudio.node ``` and see if anything is unresolved.

If one of the .so files could not be found it would show as unresolved instead of a path. This is what I get... ``` linux-vdso.so.1 => (0x00007fffa21ff000) libportaudio.so.2 =>...

I don't sorry it's been a long time. Hope you can glean something from the code and it helps in someway.

This is what worked for me... ``` lazy(myStream) .on('end', function() { console.log('end'); } .lines .forEach(function(line) { console.log(line); }); ```