Can't install Nvidia libraries and compilation problems

Started by PhilB, February 19, 2017, 05:10:40 PM

Previous topic - Next topic

PhilB

Thank you for your answers.
I have typed all the commands of your posts and even intalled git.
Still no luck with my Intel Core I5. It seems to stop at the same place.
I join the log from /temp.

PhilB

bash bootStrap.bash --deb --without-qt4

I obtain the following deb files :

avidemux3-cli-2.6.18-170221-dev.deb
avidemux3-cli-2.6.18-170221-runtime.deb
avidemux3-core-2.6.18-170221-dev.deb
avidemux3-core-2.6.18-170221-runtime.deb
avidemux3-plugins-CLI-2.6.18-170221-plugins.deb
avidemux3-plugins-COMMON-2.6.18-170221-plugins.deb
avidemux3-settings-2.6.18-170221-settings.deb

Missing files are :
avidemux3-plugins-qt5-2.6.18-170219-plugins.deb
avidemux3-qt5-2.6.18-170219-runtime.deb

mean

MAke sure you have qt5 packages installed
qttools5-dev-tools qtbase5-dev libqt5opengl5-dev

eumagga0x2a

Quote from: PhilB on February 21, 2017, 10:20:04 PM
bash bootStrap.bash --deb --without-qt4

I obtain the following deb files : [...]

Missing files are :
avidemux3-plugins-qt5-2.6.18-170219-plugins.deb
avidemux3-qt5-2.6.18-170219-runtime.deb

You get what you asked for (--without-qt4 disables Qt dependent parts alltogether). I agree that the name of this option is not quite intuitive ;)

eumagga0x2a

By the way, what did you change for the core build to succeed?

I could not find in your logbuildCore{,_debug} at the first glance an explaination why the ffmpeg build fails, unfortunately. The log bitches a lot about C++-isms in Avidemux ffmpeg patches for hevc_parser.c though (which is not related to the failure, but still).

PhilB

Xubuntu 16.04 LTS - Intel Core I5 - 16 GB ram
Command line  :
bash bootStrap.bash --deb --with-clang

In attachment log for CLI, CORE, PLUGINS and QT5


eumagga0x2a

@PhilB:

In http://avidemux.org/smif/index.php/topic,17468.msg79413.html#msg79413 you didn't build with clang, but the build of the bundled ffmpeg succeeded nevertherless. The question remains: what did you do differently for the core build with gcc to succeed? If the answer is "nothing", then you should check system logs for I/O errors and run memtest to try to identify the hardware or data corruption issue your computer is probably suffering from.

Jan Gruuthuse

Quote from: mean on February 22, 2017, 06:30:38 AM
MAke sure you have qt5 packages installed
qttools5-dev-tools qtbase5-dev libqt5opengl5-dev
Check if these are installed:
dpkg -l qttools5-dev-tools qtbase5-dev libqt5opengl5-dev
Quoteii  libqt5opengl5-dev:amd64        5.5.1+dfsg-16ubuntu7 amd64                Qt 5 OpenGL library development files
ii  qtbase5-dev:amd64              5.5.1+dfsg-16ubuntu7 amd64                Qt 5 base development files
ii  qttools5-dev-tools             5.5.1-3build1        amd64                Qt 5 development tools
If not all 3 showing ii
Please do (re)install:
sudo apt-get update && sudo apt-get install qttools5-dev-tools qtbase5-dev libqt5opengl5-dev

ps:
- click on [Select] form Code: [Select]
- the code section is now marked (selected)
- right mouse click on selection and select copy in pop-up menu
- in Terminal window right mouse click and select paste, press enter
- the commands should be executed
just in case, ...

PhilB

I have checked everything. RAM, hard drives, all needed libraries are here.
I give up and will use the appImage.
Thanks for your help.

PhilB

I downloaded from fosshub v 2.6.18 final - md5 947176e91a2a7fcd6790da7c0f19d5e3

bash bootStrap.bash --deb stopped before the end (buildCore)
but
bash bootStrap.bash --deb --with-cli successfully built the 10 deb files.

It worked once and I won't bet that if I type the same command with the same version it will work twice. Maybe that was luck... or the comp was in a good mood ...

I have kept and archived the logs coming from the /tmp directory.