Tiny Core Linux

Tiny Core Extensions => TCE Talk => Topic started by: aus9 on October 23, 2012, 03:52:28 PM

Title: [SOLVED] libva.tcz has been rebuilt
Post by: aus9 on October 23, 2012, 03:52:28 PM
EDIT subject changed to reflect new status

hi blofsy

if I unsquash libva.tcz, I see the structure includes libva.tcz.

This leads to the following result

Code: [Select]
ls /
bin/  etc/   init  libva.tcz  opt/   root/  sbin/  tmp/  var/
dev/  home/  lib/  mnt/       proc/  run/   sys/   usr/

At your earliest convenience can you rebuild please?

cheers

gordon

Title: Re: libva.tcz may need a rebuild please
Post by: Rich on October 23, 2012, 05:35:11 PM
Hi aus9
blofsy hasn't logged in to the forum in two months, you might want to try PMing him.
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 12:50:12 AM
ok will do ......aaaah I can see a similar thread that might indicate what might happen

http://forum.tinycorelinux.net/index.php/topic,8892.msg48501.html#msg48501
Title: Re: libva.tcz may need a rebuild please
Post by: blofsy on October 24, 2012, 01:32:21 AM
Hi aus9,

Sadly I won't have the time in the future to care for the packages I made but you can reaquest someone to take over. I gladly accept it.

Cheers,

blofsy
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 01:32:54 AM
wow thanks for quick reply ok will do
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 01:35:32 AM
ok for anyone with more skills me, thats should be the world here is what I have so far

Code: [Select]
libva-1.1.0$ ./configure --prefix=/usr/local
checking for a BSD-compatible install... /usr/local/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/local/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /usr/local/bin/sed
checking for grep that handles long lines and -e... /usr/local/bin/grep
checking for egrep... /usr/local/bin/grep -E
checking for fgrep... /usr/local/bin/grep -F
checking for ld used by gcc... /usr/local/bin/ld
checking if the linker (/usr/local/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/local/bin/nm -B
checking the name lister (/usr/local/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 32768
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/local/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/local/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/local/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/local/bin/ld
checking if the linker (/usr/local/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/local/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/local/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether gcc and cc understand -c and -o together... yes
checking for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for ANSI C header files... (cached) yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking whether __attribute__((visibility())) is supported... yes
checking for DRM... yes
checking for X11... no
checking for XEXT... no
checking for XFIXES... no
checking for EGL... no
checking EGL/egl.h usability... yes
checking EGL/egl.h presence... yes
checking for EGL/egl.h... yes
checking for eglGetDisplay in -lEGL... yes
checking for WAYLAND... no
checking for wayland-scanner... /bin/false
configure: creating ./config.status
config.status: creating Makefile
config.status: creating debian.upstream/Makefile
config.status: creating debian.upstream/changelog
config.status: creating debian.upstream/control
config.status: creating debian.upstream/libva1.install
config.status: creating debian.upstream/libva-drm1.install
config.status: creating debian.upstream/libva-egl1.install
config.status: creating debian.upstream/libva-glx1.install
config.status: creating debian.upstream/libva-wayland1.install
config.status: creating debian.upstream/libva-x11-1.install
config.status: creating doc/Makefile
config.status: creating dummy_drv_video/Makefile
config.status: creating pkgconfig/Makefile
config.status: creating pkgconfig/libva-drm.pc
config.status: creating pkgconfig/libva-egl.pc
config.status: creating pkgconfig/libva-glx.pc
config.status: creating pkgconfig/libva-tpi.pc
config.status: creating pkgconfig/libva-wayland.pc
config.status: creating pkgconfig/libva-x11.pc
config.status: creating pkgconfig/libva.pc
config.status: creating test/Makefile
config.status: creating test/basic/Makefile
config.status: creating test/common/Makefile
config.status: creating test/decode/Makefile
config.status: creating test/encode/Makefile
config.status: creating test/putsurface/Makefile
config.status: creating test/v4l_h264/Makefile
config.status: creating test/v4l_h264/decode/Makefile
config.status: creating test/v4l_h264/encode/Makefile
config.status: creating test/vainfo/Makefile
config.status: creating va/Makefile
config.status: creating va/drm/Makefile
config.status: creating va/egl/Makefile
config.status: creating va/glx/Makefile
config.status: creating va/va_version.h
config.status: creating va/wayland/Makefile
config.status: creating va/wayland/protocol/Makefile
config.status: creating va/x11/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands

libva - 1.1.0 (VA-API 0.33.0)

Installation prefix .............. : /usr/local
Default driver path .............. : ${exec_prefix}/lib/dri
Extra window systems ............. : drm
Build dummy driver ............... : yes
Build documentation .............. : no


Code: [Select]
tc@box:~/Downloads/libva-1.1.0$ make -j3
make  all-recursive
make[1]: Entering directory `/home/tc/Downloads/libva-1.1.0'
Making all in va
make[2]: Entering directory `/home/tc/Downloads/libva-1.1.0/va'
Making all in drm
make[3]: Entering directory `/home/tc/Downloads/libva-1.1.0/va/drm'
  CC     va_drm.lo
  CC     va_drm_auth.lo
  CC     va_drm_utils.lo
  CCLD   libva_drm.la
make[3]: Leaving directory `/home/tc/Downloads/libva-1.1.0/va/drm'
make[3]: Entering directory `/home/tc/Downloads/libva-1.1.0/va'
  CC     va.lo
  CC     va_fool.lo
  CC     va_trace.lo
  CC     va_tpi.lo
  CCLD   libva.la
  CCLD   libva-tpi.la
  CCLD   libva-drm.la
make[3]: Leaving directory `/home/tc/Downloads/libva-1.1.0/va'
make[2]: Leaving directory `/home/tc/Downloads/libva-1.1.0/va'
Making all in dummy_drv_video
make[2]: Entering directory `/home/tc/Downloads/libva-1.1.0/dummy_drv_video'
make[2]: *** No rule to make target `../va/libva-x11.la', needed by `dummy_drv_video.la'.  Stop.
make[2]: *** Waiting for unfinished jobs....
  CC     dummy_drv_video.lo
  CC     object_heap.lo
make[2]: Leaving directory `/home/tc/Downloads/libva-1.1.0/dummy_drv_video'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/tc/Downloads/libva-1.1.0'
make: *** [all] Error 2
tc@box:~/Downloads/libva-1.1.0$
Title: Re: libva.tcz may need a rebuild please
Post by: Juanito on October 24, 2012, 02:36:33 AM
I'd guess this is the key:
Code: [Select]
checking for X11... no
checking for XEXT... no
checking for XFIXES... no

..you need Xorg-7.6-dev
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 04:05:59 AM
yeah I thought so too but
Code: [Select]
tce-load -i Xorg-7.6-dev
Xorg-7.6-dev is already installed!
tc@box:~/Downloads/libva-1.1.0$ tce-load -i Xorg-7.6-lib
Xorg-7.6-lib is already installed!

edit a google has a nice link but can't tell if its useful
http://www.linuxintro.org/wiki/Error_messages_and_their_solutions
Title: Re: libva.tcz may need a rebuild please
Post by: Juanito on October 24, 2012, 04:11:31 AM
is there anything in config.log?
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 04:32:45 AM
yes first my output
Code: [Select]
tce-load -i libx11-xcb
libx11-xcb is already installed!
tc@box:~/Downloads/libva-1.1.0$ sudo find / -name xcb.pc
/mnt/sda1/usr/lib/i386-linux-gnu/pkgconfig/xcb.pc

redid configure only and compiletc is loaded by ondemand as most of those libs are as well.

culled log shows multiple errors including
Quote
configure:3656: gcc -qversion >&5
gcc: error: unrecognized option '-qversion'
gcc: fatal error: no input files
compilation terminated.

configure:7440: gcc -E  conftest.c
conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
compilation terminated.

configure:17161: result: no
Package xcb was not found in the pkg-config search path.
Perhaps you should add the directory containing `xcb.pc'
to the PKG_CONFIG_PATH environment variable
Package 'xcb', required by 'X11', not found

maybe I need more packages than compiletc?

I can upload full log if you like?
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 04:56:41 AM
tried apps panel....pulldown using provides....... search ......ac_nonexistent.h
no hits

Title: Re: libva.tcz may need a rebuild please
Post by: Juanito on October 24, 2012, 04:57:28 AM
/mnt/sda1/usr/lib/i386-linux-gnu/pkgconfig/xcb.pc

eh? It should be /usr/local/lib/pkgconfig/x11-xcb.pc [from libx11-xcb.tcz]
and /usr/local/lib/pkgconfig/xcb.pc [from libxcb-dev.tcz]
Title: Re: libva.tcz may need a rebuild please
Post by: Juanito on October 24, 2012, 05:13:01 AM
I just tried with libva-1.0.16.tar.bz2:
Code: [Select]
$ tce-load -i compiletc Xorg-7.6-dev
$ ./configure --prefix=/usr/local
$ make
$ sudo make install

..works fine
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 05:16:57 AM
just rebooted, I solved that xcb issue.....it was because I had some packages ondemand, they are now onboot.
original error remains and log
http://ompldr.org/vZzA3cA/config.log

but since you have solved it already, feel free to be maintainer as obviously I lack the skills to understand the log etc
Title: Re: libva.tcz may need a rebuild please
Post by: Juanito on October 24, 2012, 05:31:40 AM
...as obviously I lack the skills to understand the log etc

I don't think it's that - something else must be wrong, all that's needed is compiletc and Xorg-7.6-dev.
There shouldn't be any need for libxcb and, as per config.log, the configure script is not looking for it.

To understand better where you stand when compiling, I wouldn't recommend to have compiletc or any *-dev extensions "onboot" or "ondemand", but rather to load them one by one from a terminal window to check for confirmation that they're loaded, any errors, etc.

Give it another try - you never know, it might just work this time  :)
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 05:35:20 AM
ok I will but the log did mention xcb.

leaping ahead, if I build it do I need to forewarn the vlc and related maintainers or will they twig when I announce it in tce news as the current maintainer has already given permission for someone to take it over?

I don't want my vlc maintainer to build it once and then have to do it again when I or someone submits a bumped libva

thanks for your help btw
Title: Re: libva.tcz may need a rebuild please
Post by: Juanito on October 24, 2012, 05:45:02 AM
ok I will but the log did mention xcb.
Sorry - I meant config.log from my compile test run. Your link is blocked here so I couldn't check.

Quote
leaping ahead, if I build it do I need to forewarn the vlc and related maintainers or will they twig when I announce it in tce news as the current maintainer has already given permission for someone to take it over?
I think if you add your username to the last update line in the new info file it should be OK, for example:
Quote
Change-log:  2012/02/18 Original
                    ssp patch applied (juanito)
Current:        2012/10/22
Title: Re: libva.tcz may need a rebuild please
Post by: Rich on October 24, 2012, 06:17:42 AM
Hi Juanito
Here are the contents of the link that aus9 posted, feel free to delete the attachment when your are done.

Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 06:21:39 AM
sorry no need

I was missing one xcb package, config and stuff now work will submit in the fullness of time
Title: Re: libva.tcz may need a rebuild please
Post by: Rich on October 24, 2012, 06:29:32 AM
Hi aus9
I didn't see it mentioned anywhere in this thread, but the Wiki says:
Quote
Suggested compiler flags (for compatibility):
export CFLAGS="-march=i486 -mtune=i686 -Os -pipe"
export CXXFLAGS="-march=i486 -mtune=i686 -Os -pipe"
export LDFLAGS="-Wl,-O1"
You need to run those export commands so that the code produced is 486 compatible. Don't run those commands
from a script, their values will disappear as soon as the script finishes executing.

Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 06:46:22 AM
will do, making a build script now may not finish it tonite EDIT, this morning script changed and more testing
Quote
#!/bin/sh

### build your info file and copy into /tmp before running script

# build depends
tce-load -i compiletc Xorg-7.6-dev libx11-xcb libxcb-dev submitqc4 wget
# I prefer wget to use no clobber as I retest the script
export CFLAGS="-march=i486 -mtune=i686 -Os -pipe"
export CXXFLAGS="-march=i486 -mtune=i686 -Os -pipe"
export LDFLAGS="-Wl,-O1"

# download and unpack stuff
cd /tmp
wget -nc http://www.freedesktop.org/software/vaapi/releases/libva/libva-1.1.0.tar.bz2
wget -nc http://www.freedesktop.org/software/vaapi/releases/libva/libva-1.1.0.tar.bz2.sha1sum
cat libva-1.1.0.tar.bz2.sha1sum
sha1sum libva-1.1.0.tar.bz2
tar jxvf libva-1.1.0.tar.bz2


# build as per wiki
cd libva-1.1.0
./configure --prefix=/usr/local
make -j3
make DESTDIR=/tmp/libva install
echo 'needs a complying COPYING file'
mkdir -p /tmp/libva/usr/local/share/doc/libva
cp -f COPYING /tmp/libva/usr/local/share/doc/libva
# nothing to strip

# start tcz stuff
mkdir -p /tmp/libva/usr/local/tce.installed
touch /tmp/libva/usr/local/tce.installed/libva
sudo chown -R root:staff /tmp/libva/usr/local/tce.installed
sudo chmod -R 775 /tmp/libva/usr/local/tce.installed
cd /tmp
mksquashfs libva libva.tcz
md5sum libva.tcz > libva.tcz.md5.txt
cd libva
find usr -not -type d > libva.tcz.list
cp -f libva.tcz.list /tmp
cd /tmp
submitqc4

will do more later...wiki looks wrong IMHO as per next post
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 07:18:59 AM
Rich

the wiki has me doing a squash before I have created (touched) an installed file (tce.installed)

I will amend my script in a moment after test

and those chown need sudo ....if you agree I will fix later...in the wiki
Title: Re: libva.tcz may need a rebuild please
Post by: Rich on October 24, 2012, 01:48:11 PM
Hi aus9
Quote
the wiki has me doing a squash before I have created (touched) an installed file (tce.installed)
Moving the section titled:  Adding Custom Startup Scripts  just above:  Creating a .tcz  would make more sense.
Quote
and those chown need sudo
Since the Wiki does not state you need to be running as root, I'm inclined to agree.
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 24, 2012, 06:52:36 PM
Rich

I have split custom script section to highlight the new section and created a license warning. BTW I saw a post from bmarkus on a similar theme, which is the reason why I think we need the addition

http://forum.tinycorelinux.net/index.php/topic,14083.0.html
Title: Re: libva.tcz may need a rebuild please
Post by: Rich on October 24, 2012, 09:51:22 PM
Hi aus9
I took a look at the Wiki page, and as far as I can tell, it looks good.
Title: Re: libva.tcz may need a rebuild please
Post by: aus9 on October 28, 2012, 04:51:45 PM
rather than post a news item, I will mention it here

new libva has hit the main mirror.

thanks to Juanito and Rich for your help

cheers