error building fits_web_ql (ubuntu 18 cloud vm with no assosiated GPU) about fits_web_ql

[jvo203]

Is this still an open issue? Such errors would usually be caused by a non-standard location of the manually-compiled/locally-installed libvpx, in which case playing with the following environment variables (ideally set in .bashrc etc.) should solve the problem:

export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib

[skitaeff]

No, it is no longer an issue. You can close it. Thanks, Slava

…

Sent from my iPhone On 8 Mar 2019, at 10:59 am, jvo203 <[email protected]<mailto:[email protected]>> wrote: Is this still an open issue? Such errors would usually be caused by a non-standard location of the manually-compiled/locally-installed libvpx, in which case playing with the following environment variables (ideally set in .bashrc etc.) should solve the problem: export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#2 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABKvSDxn-3KRAWkBeDlGC4OKdOjuzHoQks5vUkKigaJpZM4bYKs9>.

[alitimer]

Thanks for your reply; already addressed the LD_LIBRARY_PATH and PKG_CONFIG_PATH, however stuck in the above error. Not sure about the VM because it's working on native Ubuntu and this happens on a cloud vm!

[jvo203]

After correcting the LD_LIBRARY_PATH and PKG_CONFIG_PATH, if the issue still persists you could issue "cargo clean" from within the fits_web_ql folder and then re-try cargo build. There may be some stale settings remaining in a cargo cache from previous failed cargo build runs, which the "cargo clean" command should resolve. As per Slava's comment, I will close this issue then.

[jvo203]

An additional comment: FITSWebQL Fe (Rust edition) is known to work well on Intel Clear Linux running on Microsoft Azure cloud (tested last year). If you are feeling adventurous you could give it at try. Here are the extra steps needed to get it to work on Intel Clear Linux:

sudo swupd bundle-add dev-utils c-basic rust-basic

manual yasm 1.3.0 compile/install from source

manual openssl compile/install from source (plus copy the certificates from /etc/... to /usr/local/...)

tcl from source (tcl-basic does not provide tcl.h)

NGINX reverse proxy

launching: sudo nginx

configuration: cat /etc/nginx/nginx.conf
worker_processes 4;

events {
worker_connections 1024;
}

http {
include mime.types;
default_type application/octet-stream;

sendfile      on;
aio           on;
tcp_nopush    on;
directio      8m;

access_log    syslog:server=unix:/dev/log;

map $http_upgrade $connection_upgrade {
    default upgrade;
    '' close;
}

upstream websocket {
    server 127.0.0.1:8080;
}

server {
    listen 80 default;
    location / {
        proxy_set_header   X-Real-IP        $remote_addr;
        proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;
        proxy_set_header   Host             $host;

        proxy_pass http://127.0.0.1:8080/;

    }

	location /fitswebql/websocket {
        proxy_pass http://websocket;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
    }
}



#include /etc/nginx/conf.d/*.conf;

}