Recherche avancée

Sur d’autres sites (7271)

• Issue #1 when compiling Xuggler for Raspberry pi with libspeex

  23 juillet 2014, par Ashish Sharma

  I am trying to compile Xuggler for Raspberry Pi(Running on Debian OS aka Raspbian),

  I followed the ’Basic Build Instructions’ available here for compiling Xuggler.

  After I successfully installed all the prerequisites and set the correct paths, I ran the following command :

  ant run-tests

  After sometime I am facing the following error and the ant build fails :

  scroll at the end of log to see the issue

   [exec] Making all in libspeex
  
   [exec] make[2]: Entering directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex'
  
   [exec] Incarcerated package must be reconfigured; regenerating out of date captive Makefile from: ../../../../../captive/libspeex/csrc/configure
  
   [exec] /bin/mkdir -p csrc
  
   [exec] cd csrc && sh ../incarcerate
  
   [exec] checking for a BSD-compatible install... /usr/bin/install -c
  
   [exec] checking whether build environment is sane... yes
  
   [exec] checking for a thread-safe mkdir -p... /bin/mkdir -p
  
   [exec] checking for gawk... no
  
   [exec] checking for mawk... mawk
  
   [exec] checking whether make sets $(MAKE)... yes
  
   [exec] checking build system type... armv6l-unknown-linux-gnu
  
   [exec] checking host system type... armv6l-unknown-linux-gnu
  
   [exec] checking how to print strings... printf
  
   [exec] checking for style of include used by make... GNU
  
   [exec] checking for gcc... gcc
  
   [exec] checking whether the C compiler works... yes
  
   [exec] checking for C compiler default output file name... a.out
  
   [exec] checking for suffix of executables...
  
   [exec] checking whether we are cross compiling... no
  
   [exec] checking for suffix of object files... o
  
   [exec] checking whether we are using the GNU C compiler... yes
  
   [exec] checking whether gcc accepts -g... yes
  
   [exec] checking for gcc option to accept ISO C89... none needed
  
   [exec] checking dependency style of gcc... none
  
   [exec] checking for a sed that does not truncate output... /bin/sed
  
   [exec] checking for grep that handles long lines and -e... /bin/grep
  
   [exec] checking for egrep... /bin/grep -E
  
   [exec] checking for fgrep... /bin/grep -F
  
   [exec] checking for ld used by gcc... /usr/bin/ld
  
   [exec] checking if the linker (/usr/bin/ld) is GNU ld... yes
  
   [exec] checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
  
   [exec] checking the name lister (/usr/bin/nm -B) interface... BSD nm
  
   [exec] checking whether ln -s works... yes
  
   [exec] checking the maximum length of command line arguments... 805306365
  
   [exec] checking whether the shell understands some XSI constructs... yes
  
   [exec] checking whether the shell understands "+="... yes
  
   [exec] checking how to convert armv6l-unknown-linux-gnu file names to armv6l-unknown-linux-gnu format... func_convert_file_noop
  
   [exec] checking how to convert armv6l-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
  
   [exec] checking for /usr/bin/ld option to reload object files... -r
  
   [exec] checking for objdump... objdump
  
   [exec] checking how to recognize dependent libraries... pass_all
  
   [exec] checking for dlltool... false
  
   [exec] checking how to associate runtime and link libraries... printf %s\n
  
   [exec] checking for archiver @FILE support... @
  
   [exec] checking for strip... strip
  
   [exec] checking for ranlib... ranlib
  
   [exec] checking command to parse /usr/bin/nm -B output from gcc object... ok
  
   [exec] checking for sysroot... no
  
   [exec] checking for mt... mt
  
   [exec] checking if mt is a manifest tool... no
  
   [exec] checking how to run the C preprocessor... gcc -E
  
   [exec] checking for ANSI C header files... yes
  
   [exec] checking for sys/types.h... yes
  
   [exec] checking for sys/stat.h... yes
  
   [exec] checking for stdlib.h... yes
  
   [exec] checking for string.h... yes
  
   [exec] checking for memory.h... yes
  
   [exec] checking for strings.h... yes
  
   [exec] checking for inttypes.h... yes
  
   [exec] checking for stdint.h... yes
  
   [exec] checking for unistd.h... yes
  
   [exec] checking for dlfcn.h... yes
  
   [exec] checking for objdir... .libs
  
   [exec] checking if gcc supports -fno-rtti -fno-exceptions... no
  
   [exec] checking for gcc option to produce PIC... -fPIC -DPIC
  
   [exec] checking if gcc PIC flag -fPIC -DPIC works... yes
  
   [exec] checking if gcc static flag -static works... yes
  
   [exec] checking if gcc supports -c -o file.o... yes
  
   [exec] checking if gcc supports -c -o file.o... (cached) yes
  
   [exec] checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
  
   [exec] checking dynamic linker characteristics... GNU/Linux ld.so
  
   [exec] checking how to hardcode library paths into programs... immediate
  
   [exec] checking whether stripping libraries is possible... yes
  
   [exec] checking if libtool supports shared libraries... yes
  
   [exec] checking whether to build shared libraries... no
  
   [exec] checking whether to build static libraries... yes
  
   [exec] checking whether to enable maintainer-specific portions of Makefiles... no
  
   [exec] checking whether byte ordering is bigendian... no
  
   [exec] checking for an ANSI C-conforming const... yes
  
   [exec] checking for inline... inline
  
   [exec] checking for C/C++ restrict keyword... __restrict
  
   [exec] checking for C99 variable-size arrays... yes
  
   [exec] checking alloca.h usability... yes
  
   [exec] checking alloca.h presence... yes
  
   [exec] checking for alloca.h... yes
  
   [exec] checking getopt.h usability... yes
  
   [exec] checking getopt.h presence... yes
  
   [exec] checking for getopt.h... yes
  
   [exec] checking for alloca... yes
  
   [exec] checking for SSE in current arch/CFLAGS... no
  
   [exec] checking for ELF visibility... yes
  
   [exec] checking sys/soundcard.h usability... yes
  
   [exec] checking sys/soundcard.h presence... yes
  
   [exec] checking for sys/soundcard.h... yes
  
   [exec] checking sys/audioio.h usability... no
  
   [exec] checking sys/audioio.h presence... no
  
   [exec] checking for sys/audioio.h... no
  
   [exec] checking for Ogg... yes
  
   [exec] checking for sin in -lm... yes
  
   [exec] checking for getopt_long... yes
  
   [exec] checking for main in -lwinmm... no
  
   [exec] checking for pkg-config... /usr/bin/pkg-config
  
   [exec] checking pkg-config is at least version 0.9.0... yes
  
   [exec] checking size of short... 0
  
   [exec] checking size of int... 0
  
   [exec] checking size of long... 0
  
   [exec] configure: creating ./config.status
  
   [exec] config.status: creating Makefile
  
   [exec] config.status: creating libspeex/Makefile
  
   [exec] config.status: creating src/Makefile
  
   [exec] config.status: creating doc/Makefile
  
   [exec] config.status: creating Speex.spec
  
   [exec] config.status: creating include/Makefile
  
   [exec] config.status: creating include/speex/Makefile
  
   [exec] config.status: creating speex.pc
  
   [exec] config.status: creating speexdsp.pc
  
   [exec] config.status: creating win32/Makefile
  
   [exec] config.status: creating win32/libspeex/Makefile
  
   [exec] config.status: creating win32/speexenc/Makefile
  
   [exec] config.status: creating win32/speexdec/Makefile
  
   [exec] config.status: creating symbian/Makefile
  
   [exec] config.status: creating win32/VS2003/Makefile
  
   [exec] config.status: creating win32/VS2003/tests/Makefile
  
   [exec] config.status: creating win32/VS2003/libspeex/Makefile
  
   [exec] config.status: creating win32/VS2003/libspeexdsp/Makefile
  
   [exec] config.status: creating win32/VS2003/speexdec/Makefile
  
   [exec] config.status: creating win32/VS2003/speexenc/Makefile
  
   [exec] config.status: creating win32/VS2005/Makefile
  
   [exec] config.status: creating win32/VS2005/libspeex/Makefile
  
   [exec] config.status: creating win32/VS2005/speexdec/Makefile
  
   [exec] config.status: creating win32/VS2005/speexenc/Makefile
  
   [exec] config.status: creating win32/VS2005/libspeexdsp/Makefile
  
   [exec] config.status: creating win32/VS2005/tests/Makefile
  
   [exec] config.status: creating win32/VS2008/libspeexdsp/Makefile
  
   [exec] config.status: creating win32/VS2008/Makefile
  
   [exec] config.status: creating win32/VS2008/speexdec/Makefile
  
   [exec] config.status: creating win32/VS2008/tests/Makefile
  
   [exec] config.status: creating win32/VS2008/libspeex/Makefile
  
   [exec] config.status: creating win32/VS2008/speexenc/Makefile
  
   [exec] config.status: creating include/speex/speex_config_types.h
  
   [exec] config.status: creating ti/Makefile
  
   [exec] config.status: creating ti/speex_C54_test/Makefile
  
   [exec] config.status: creating ti/speex_C55_test/Makefile
  
   [exec] config.status: creating ti/speex_C64_test/Makefile
  
   [exec] config.status: creating config.h
  
   [exec] config.status: executing depfiles commands
  
   [exec] config.status: executing libtool commands
  
   [exec] Type "make; make install" to compile and install Speex
  
   [exec] Incarcerated package configured: ../../../../../captive/libspeex
  
   [exec] Incarcerating package ../../../../../captive/libspeex to fake DESTDIR=/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage
  
   [exec] make[3]: Entering directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex/csrc'
  
   [exec] make  all-recursive
  
   [exec] make[4]: Entering directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex/csrc'
  
   [exec] Making all in libspeex
  
   [exec] make[4]: *** [all-recursive] Error 1
  
   [exec] make[3]: *** [all] Error 2
  
   [exec] make[4]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex/csrc'
  
   [exec] make[3]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex/csrc'
  
   [exec] Out of date files; re-running make
  
   [exec] make[3]: Entering directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex/csrc'
  
   [exec] make  all-recursive
  
   [exec] make[4]: Entering directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex/csrc'
  
   [exec] Making all in libspeex
  
   [exec] make[5]: Entering directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex/csrc/libspeex'
  
   [exec] /bin/bash ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/../../../../captive/libspeex/csrc/libspeex -I.. -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/../../../../captive/libspeex/csrc/include -I../include -I.. -I/home/pi/Downloads/xuggler/include     -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include  -fvisibility=hidden -O3 -msse -c -o cb_search.lo /home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/../../../../captive/libspeex/csrc/libspeex/cb_search.c
  
   [exec] libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/../../../../captive/libspeex/csrc/libspeex -I.. -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/../../../../captive/libspeex/csrc/include -I../include -I.. -I/home/pi/Downloads/xuggler/include -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include -fvisibility=hidden -O3 -msse -c /home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/../../../../captive/libspeex/csrc/libspeex/cb_search.c  -fPIC -DPIC -o cb_search.o
  
   [exec] cc1: error: unrecognized command line option '-msse'
  
   [exec] make[5]: *** [cb_search.lo] Error 1
  
   [exec] make[4]: *** [all-recursive] Error 1
  
   [exec] make[3]: *** [all] Error 2
  
   [exec] make[2]: *** [all-local] Error 2
  
   [exec] make[1]: *** [all-recursive] Error 1
  
   [exec] make: *** [all-recursive] Error 1
  
   [exec] make[5]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex/csrc/libspeex'
  
   [exec] make[4]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex/csrc'
  
   [exec] make[3]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex/csrc'
  
   [exec] make[2]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libspeex'
  
   [exec] make[1]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive'
  
  
  
  BUILD FAILED
  
  /home/pi/Downloads/xuggle-xuggler/mk/buildtools/buildhelper.xml:1192: exec returned: 2
  
  
  
  Total time: 73 minutes 17 seconds

  I am unable to understand the problem statment "unrecognized command line option ’-msse’" here, Can someone please tell me how can I resolve this or circumvent it in xuggler ?

• Small Time DevOps

  1er janvier 2021, par Multimedia Mike — General

  When you are a certain type of nerd who has been on the internet for long enough, you might run the risk of accumulating a lot of projects and websites. Website-wise, I have this multimedia.cx domain on which I host a bunch of ancient static multimedia documents as well as this PHP/MySQL-based blog. Further, there are 3 other PHP/MySQL-based blogs hosted on subdomains. Also, there is the wiki, another PHP/MySQL web app. A few other custom PHP- and Python-based apps are running around on the server as well.

  While things largely run on auto-pilot, I need to concern myself every now and then with their ongoing upkeep.

  If you ask N different people about the meaning of the term ‘DevOps’, you will surely get N different definitions. However, whenever I have to perform VM maintenance, I like to think I am at least dipping my toes into the DevOps domain. At the very least, the job seems to be concerned with making infrastructure setup and upgrades reliable and repeatable.

  Even if it’s not fully automated, at the very least, I have generated a lot of lists for how to make things work (I’m a big fan of Trello’s Kanban boards for this), so it gets easier every time (ideally, anyway).

  Infrastructure History

  For a solid decade, from 2004 to 2014, everything was hosted on shared, cPanel-based web hosting. In mid-2014, I moved from the shared hosting over to my own VPSs, hosted on DigitalOcean. I must have used Ubuntu 14.04 at the time, as I look down down the list of Ubuntu LTS releases. It was with much trepidation that I undertook this task (knowing that anything that might go wrong with the stack, from the OS up to the apps, would all be firmly my fault), but it turned out not to be that bad. The earliest lesson you learn for such a small-time setup is to have a frontend VPS (web server) and a backend VPS (database server). That way, a surge in HTTP requests has no chance of crashing the database server due to depleted memory.

  At the end of 2016, I decided to refresh the VMs. I brought them up to Ubuntu 16.04 at the time.

  Earlier this year, I decided it would be a good idea to refresh the VMs again since it had been more than 3 years. The VMs were getting long in the tooth. Plus, I had seen an article speculating that Azure, another notable cloud hosting environment, might be getting full. It made me feel like I should grab some resources while I still could (resource-hoarding was in this year).

  I decided to use 18.04 for these refreshed VMs, even though 20.04 was available. I think I was a little nervous about 20.04 because I heard weird things about something called snap packages being the new standard for distributing software for the platform and I wasn’t ready to take that plunge.

  Which brings me to this month’s VM refresh in which I opted to take the 20.04 plunge.

  Oh MediaWiki

  I’ve been the maintainer and caretaker of the MultimediaWiki for 15 years now (wow ! Where does the time go ?). It doesn’t see a lot of updating these days, but I know it still serves as a resource for lots of obscure technical multimedia information. I still get requests for new accounts because someone has uncovered some niche technical data and wants to make sure it gets properly documented.

  MediaWiki is quite an amazing bit of software and it undergoes constant development and improvement. According to the version history, I probably started the MultimediaWiki with the 1.5 series. As of this writing, 1.35 is the latest and therefore greatest lineage.

  This pace of development can make it a bit of a chore to keep up to date. This was particularly true in the old days of the shared hosting when you didn’t have direct shell access and so it’s something you put off for a long time.

  Honestly, to be fair, the upgrade process is pretty straightforward :

  1. Unpack a set of new files on top of the existing tree
  2. Run a PHP script to perform any database table upgrades

  Pretty straightforward, assuming that there are no hiccups along the way, right ? And the vast majority of the time, that’s the case. Until it’s not. I had an upgrade go south about a year and a half ago (I wasn’t the only MW installation to have the problem at the time, I learned). While I do have proper backups, it still threw me for a loop and I worked for about an hour to restore the previous version of the site. That experience understandably left me a bit gun-shy about upgrading the wiki.

  But upgrades must happen, especially when security notices come out. Eventually, I created a Trello template with a solid, 18-step checklist for upgrading MW as soon as a new version shows up. It’s still a chore, just not so nerve-wracking when the steps are all enumerated like that.

  As I compose the post, I think I recall my impetus for wanting to refresh from the 16.04 VM. 16.04 used PHP 7.0. I wanted to upgrade to the latest MW, but if I tried to do so, it warned me that it needed PHP 7.4. So I initialized the new 18.04 VM as described above… only to realize that PHP 7.2 is the default on 18.04. You need to go all the way to 20.04 for 7.4 standard. I’m sure it’s possible to install later versions of PHP on 16.04 or 18.04, but I appreciate going with the defaults provided by the distro.

  I figured I would just stay with MediaWiki 1.34 series and eschew 1.35 series (requiring PHP 7.4) for the time being… until I started getting emails that 1.34 would go end-of-life soon. Oh, and there are some critical security updates, but those are only for 1.35 (and also 1.31 series which is still stubbornly being maintained for some reason).

  So here I am with a fresh Ubuntu 20.04 VM running PHP 7.4 and MediaWiki 1.35 series.

  How Much Process ?

  Anyone who decides to host on VPSs vs, say, shared hosting is (or ought to be) versed on the matter that all your data is your own problem and that glitches sometimes happen and that your VM might just suddenly disappear. (Indeed, I’ve read rants about VMs disappearing and taking entire un-backed-up websites with them, and also watched as the ranters get no sympathy– “yeah, it’s a VM ; the data is your responsibility”) So I like to make sure I have enough notes so that I could bring up a new VM quickly if I ever needed to.

  But the process is a lot of manual steps. Sometimes I wonder if I need to use some automation software like Ansible in order to bring a new VM to life. Why do that if I only update the VM once every 1-3 years ? Well, perhaps I should update more frequently in order to ensure the process is solid ?

  Seems like a lot of effort for a few websites which really don’t see much traffic in the grand scheme of things. But it still might be an interesting exercise and might be good preparation for some other websites I have in mind.

  Besides, if I really wanted to go off the deep end, I would wrap everything up in containers and deploy using D-O’s managed Kubernetes solution.

  The post Small Time DevOps first appeared on Breaking Eggs And Making Omelettes.

• Revision 34808 : class url pour le lien et non org (site VS société, merci tetue)

  31 janvier 2010, par brunobergot@… — Log

  class url pour le lien et non org (site VS société, merci tetue)