pluggable-output-processor icon indicating copy to clipboard operation
pluggable-output-processor copied to clipboard

nothing happens when i call make, g++ ...

Open frruit opened this issue 8 years ago • 5 comments
trafficstars

Hi today i was happy to find your solution for colorizing terminal output for different tools. I'm working on ubuntu 16 and have to following problem after executing your instructions from the tutorial

When i call make inside the terminal nothing happens. I see only the cursor is blinking. The symlink seems to work. Here is mine configuration: Link to: /usr/local/bin/outproc Links: /home/username/.local/bin/make

Hope u can help me.

Best regards frruit

frruit avatar Sep 15 '17 12:09 frruit

I'll try :) what exactly Ubuntu do you have? 16.04 (xenial) or 16.10 (yakkety) ? I'll use the corresponding docker container to check it on my spare time...

On Fri, Sep 15, 2017 at 2:41 PM, frruit [email protected] wrote:

Hi today i was happy to find your solution for colorizing terminal output for different tools. I'm working on ubuntu 16 and have to following problem after executing your instructions from the tutorial

When i call make inside the terminal nothing happens. I see only the cursor is blinking. The symlink seems to work. Here is mine configuration: Link to: /usr/local/bin/outproc Links: /home/username/.local/bin/make

Hope u can help me.

Best regards frruit

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/zaufi/pluggable-output-processor/issues/13, or mute the thread https://github.com/notifications/unsubscribe-auth/AAhfa7CEa2pQxAzulmozSWDx5i1b99i1ks5sinBkgaJpZM4PY6i_ .

zaufi avatar Sep 15 '17 12:09 zaufi

I have 16.04 on my machine. greate! thanks a lot!

frruit avatar Sep 15 '17 12:09 frruit

Thanks for the report, I've been able to reproduce it...

zaufi avatar Sep 17 '17 08:09 zaufi

Thanks for the report, I've been able to reproduce it... That is not really a bug, but a lack of feature. (and little bit messy in the README %)

zaufi avatar Sep 17 '17 11:09 zaufi

Nowadays outproc is looking for the enabled modules in the <install-prefix>/lib/outproc/bin/. This path must be a leading in your PATH to effectively override wrapped binaries. According to your description, you don't have it, instead, your symlink(s) is in the ~/.local/bin/. So, outproc do not recognize it as itself module and do the fork... Actually, it'll be easy to make it possible to have modules symlinks in arbitrary locations (I'll do it soon).

For now, it would help to you to install symlinks to <install-prefix>/lib/outproc/bin/ and make it a leading path in your PATH.

zaufi avatar Sep 17 '17 11:09 zaufi