This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Possible 2 bugs in Linux & vapoursynth
#8
(12.06.2020, 22:10)Selur Wrote: Hmm,.. it works so seems like the variable is inherited by the child script. (parent: build-plugins.sh, child: plugin-vslsmashsource.sh)
the log files show the right paths:
+ vsprefix=/home/selur/opt/vapoursynth
+ export PATH=/home/selur/opt/vapoursynth/bin:/home/selur/opt/vapoursynth/bin:/home/selur/.cargo/bin:/home/selur/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
+ export LD_LIBRARY_PATH=/home/selur/opt/vapoursynth/lib
+ export PYTHONUSERBASE=/home/selur/opt/vapoursynth
+ export PKG_CONFIG_PATH=/home/selur/opt/vapoursynth/lib/pkgconfig
+ pkg-config --cflags vapoursynth
+ export CFLAGS=-pipe -O3 -Wno-attributes -fPIC -fvisibility=hidden -fno-strict-aliasing -I/home/selur/opt/vapoursynth/include/vapoursynth -I/home/selur/opt/vapoursynth/include -I/usr/include/compute
+ export CXXFLAGS=-pipe -O3 -Wno-attributes -fPIC -fvisibility=hidden -fno-strict-aliasing -I/home/selur/opt/vapoursynth/include/vapoursynth -I/home/selur/opt/vapoursynth/include -I/usr/include/compute -Wno-reorder
+ export LDFLAGS=-L/home/selur/opt/vapoursynth/lib
+ ghdl HolyWu/L-SMASH-Works
+ git clone --depth 1 --recursive https://github.com/HolyWu/L-SMASH-Works build
Klone nach 'build' ...
+ cd build
+ ghdl l-smash/l-smash
+ git clone --depth 1 --recursive https://github.com/l-smash/l-smash build
Klone nach 'build' ...
+ cd build
+ ./configure --prefix=/home/selur/opt/vapoursynth --extra-cflags=-pipe -O3 -Wno-attributes -fPIC -fvisibility=hidden -fno-strict-aliasing -I/home/selur/opt/vapoursynth/include/vapoursynth -I/home/selur/opt/vapoursynth/include -I/usr/include/compute

generating config.mak ...
...
Wink

Cu Selur



Well, are you sure we have the same version of build-plugins/header.sh ? My vslsmashsource.log from your original source is :

+ export LD_LIBRARY_PATH=/usr/local/lib;/usr/local/lib/vapoursynth
+ pkg-config --cflags vapoursynth
+ export CFLAGS=-pipe -O3 -Wno-attributes -fPIC -fvisibility=hidden -fno-strict-aliasing -I/usr/local/include/vapoursynth -I/usr/local/include -I/usr/include/compute
+ export CXXFLAGS=-pipe -O3 -Wno-attributes -fPIC -fvisibility=hidden -fno-strict-aliasing -I/usr/local/include/vapoursynth -I/usr/local/include -I/usr/include/compute -Wno-reorder
+ ghdl VFR-maniac/L-SMASH-Works
+ git clone --depth 1 --recursive https://github.com/VFR-maniac/L-SMASH-Works build
Cloning into 'build'...
+ cd build
+ ghdl l-smash/l-smash
+ git clone --depth 1 --recursive https://github.com/l-smash/l-smash build
Cloning into 'build'...
+ cd build
+ ./configure --prefix= --extra-cflags=-pipe -O3 -Wno-attributes -fPIC -fvisibility=hidden -fno-strict-aliasing -I/usr/local/include/vapoursynth -I/usr/local/include -I/usr/include/compute

generating config.mak ...

SRCDIR = .
DESTDIR =
prefix = /usr/local

Note the prefix is empty in configure; configure takes the default /usr/local.
build-plugins/header.sh, first part of all plugin-build, is :

#!/bin/sh
set -e

JOBS=4

[... functions...]

set -x

export LD_LIBRARY_PATH="/usr/local/lib;/usr/local/lib/vapoursynth"
export CFLAGS="-pipe -O3 -Wno-attributes -fPIC -fvisibility=hidden -fno-strict-aliasing $(pkg-config --cflags vapoursynth) -I/usr/include/compute"
export CXXFLAGS="$CFLAGS -Wno-reorder"

These 3 exports, and their order, are coherent with my log, not your ?
Reply


Messages In This Thread
Possible 2 bugs in Linux & vapoursynth - by ALM - 10.06.2020, 00:27
RE: Possible 2 bugs in Linux & vapoursynth - by ALM - 12.06.2020, 18:29
RE: Possible 2 bugs in Linux & vapoursynth - by ALM - 12.06.2020, 20:03
RE: Possible 2 bugs in Linux & vapoursynth - by ALM - 13.06.2020, 16:12
RE: Possible 2 bugs in Linux & vapoursynth - by ALM - 13.06.2020, 16:28
RE: Possible 2 bugs in Linux & vapoursynth - by ALM - 13.06.2020, 20:44
RE: Possible 2 bugs in Linux & vapoursynth - by ALM - 15.06.2020, 18:27
RE: Possible 2 bugs in Linux & vapoursynth - by ALM - 16.06.2020, 01:41

Forum Jump:


Users browsing this thread: 1 Guest(s)