petit_miner Posted January 26, 2019 Share Posted January 26, 2019 Hi there, I'm currently working on cross compiling libva-v4l2-request to test the VPU on the Allwinner V3s. I cloned the master branch from Github and told autoreconf to cross compile, but however it keeps looking for the wrong libva and libdrm libraries. Also everything with arm-linux-gnueabi fails somehow. I hope someone can help me with that. user@workpad:~/workspace/allwinnerV3s/libva-v4l2-request$ ./autogen.sh --host=arm-linux-gnueabi --build=x86_64-linux-gnu autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, libtoolize: and rerunning libtoolize and aclocal. libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am. autoreconf: running: /usr/bin/autoconf autoreconf: running: /usr/bin/autoheader autoreconf: running: automake --add-missing --copy --no-force autoreconf: Leaving directory `.' checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-linux-gnueabi-strip... no checking for strip... strip configure: WARNING: using cross tools not prefixed with host triplet checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether UID '1000' is supported by ustar format... yes checking whether GID '1000' is supported by ustar format... yes checking how to create a ustar tar archive... gnutar checking whether make supports nested variables... (cached) yes checking build system type... x86_64-pc-linux-gnu checking host system type... arm-unknown-linux-gnueabi checking how to print strings... printf checking for style of include used by make... GNU checking for arm-linux-gnueabi-gcc... no 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... yes 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 whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... no checking for arm-linux-gnueabi-dumpbin... no checking for arm-linux-gnueabi-link... no checking for dumpbin... no checking for link... link -dump checking the name lister (nm) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking how to convert x86_64-pc-linux-gnu file names to arm-unknown-linux-gnueabi format... func_convert_file_noop checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for arm-linux-gnueabi-objdump... no checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for arm-linux-gnueabi-dlltool... no checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for arm-linux-gnueabi-ar... no checking for ar... ar checking for archiver @FILE support... @ checking for arm-linux-gnueabi-strip... strip checking for arm-linux-gnueabi-ranlib... no checking for ranlib... ranlib checking command to parse nm output from gcc object... ok checking for sysroot... no checking for a working dd... /bin/dd checking how to truncate binary pipes... /bin/dd bs=4096 count=1 checking for arm-linux-gnueabi-mt... no checking for mt... mt checking if mt 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/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 arm-linux-gnueabi-gcc... 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 whether gcc understands -c and -o together... (cached) yes checking dependency style of gcc... (cached) gcc3 checking dependency style of gcc... gcc3 checking whether byte ordering is bigendian... no 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... no checking for sin in -lm... yes checking for arm-linux-gnueabi-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for DRM... yes checking for LIBVA_DEPS... yes checking for LIBVA_DRM_DEPS... yes checking for MPEG2 support... no checking for H.264 support... no checking for H.265 support... no checking for VA drivers path... /usr/lib/x86_64-linux-gnu/dri checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating src/autoconfig.h config.status: src/autoconfig.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands v4l2_request configuration summary: VA-API version ................... : 1.1.0 VA-API drivers path .............. : /usr/lib/x86_64-linux-gnu/dri H.264 support .................... : no H.265 support .................... : no MPEG2 support .................... : no Link to comment Share on other sites More sharing options...
JMCC Posted January 26, 2019 Share Posted January 26, 2019 Since these kind of libraries are not too big, I usually compile them natively on an ARM board. V3s' CPU may be a little too weak, but you can do it on any other armhf board you have, and it won't take more than a few minutes. Link to comment Share on other sites More sharing options...
petit_miner Posted January 26, 2019 Author Share Posted January 26, 2019 Thanks, I will give it a try. Since this is a compiled library, where I should put the compiled files ? And do I have to create systemlinks or something similiar? Link to comment Share on other sites More sharing options...
TonyMac32 Posted January 26, 2019 Share Posted January 26, 2019 Hello @petit_miner, How is the status of your hardware? Is it good enough to be built for evaluation? I want to do something similar, and have some V3s's laying about because of it that need a home. Link to comment Share on other sites More sharing options...
petit_miner Posted January 27, 2019 Author Share Posted January 27, 2019 I think so, but I would suggest that you try the 4 Layer version. It has more interfaces (VGA out) and also uses 3 seperate DC DC step down modules which are easy to solder. I haven't tested the HDMI IN (ADV7611) yet, but every other interface works flawlessly. However I made a mistake while exporting the gerber files from eagle, the pcb misses the hole for the strain relief of the ethernet jack. It isn't that critical since the strain relief is made of plastic and you can easily cut it. If you want to I can sell you a bare PCB. Link to comment Share on other sites More sharing options...
Recommended Posts