Recherche avancée

Sur d’autres sites (4695)

• Error when I compile ffmpeg in Xcode5

  1er août 2014, par user3097851

  I compile ffmpeg in OSX. My xcode version is 5.1. ffmpeg configure is :

  ./configure --disable-doc --disable-ffmpeg --disable-ffplay --disable-ffserver --enable-cross-compile --arch=arm --target-os=darwin --cc=/Applications/Xcode.app/Contents/Developer/usr/bin/gcc  --as='gas-preprocessor/gas-preprocessor.pl /Applications/Xcode.app/Contents/Developer/usr/bin/gcc  ' --sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS7.1.sdk --cpu=cortex-a8 --extra-cflags='-arch armv7' --extra-ldflags='-arch armv7 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS7.1.sdk' --enable-pic --disable-asm --prefix="../lib"

  This is the error :

  /usr/bin/ranlib: object: libavfilter/libavfilter.a(aeval.o) malformed object (unknown load command 1)
  
  ar: internal ranlib command failed
  
  make: *** [libavfilter/libavfilter.a] Error 1

  I’m not sure what this error means or how to solve it.

• configure, mips : remove MIPS32R2, merging it with MIPSFPU

  5 mars 2015, par James Cowgill

  configure, mips : remove MIPS32R2, merging it with MIPSFPU
  There are no independant uses of mips32r2 instructions except for the
  
  FPU parts. Due to the heavy use of mips32r2 specifc fpu extensions, I
  
  am guessing the original author intended MIPSFPU to imply MIPS32R2 anyway.
  Since these fpu instructions are available on mips64 (non-r2), enable them
  
  there as well.
  Also remove the last occurence of HAVE_MIPS32R2 (which is coupled to
  
  HAVE_MIPSFPU anyway).
  mips32r2 is left in the list of options form compatability so that using
  
  — disable-mips32r2 doesn’t break anything.
  Signed-off-by : James Cowgill <james410@cowgill.org.uk>
  
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] Makefile
  • [DH] arch.mak
  • [DH] configure
  • [DH] libavcodec/mips/ac3dsp_mips.c

• Cloaked Archive Wiki

  16 mai 2011, par Multimedia Mike — General

  Google’s Chrome browser has made me phenomenally lazy. I don’t even attempt to type proper, complete URLs into the address bar anymore. I just type something vaguely related to the address and let the search engine take over. I saw something weird when I used this method to visit Archive Team’s site :

  
  
  

  There’s greater detail when you elect to view more results from the site :

  
  
  

  As the administrator of a MediaWiki installation like the one that archiveteam.org runs on, I was a little worried that they might have a spam problem. However, clicking through to any of those out-of-place pages does not indicate anything related to pharmaceuticals. Viewing source also reveals nothing amiss.

  I quickly deduced that this is a textbook example of website cloaking. This is when a website reports different content to a search engine than it reports to normal web browsers (humans, presumably). General pseudocode :

  PLAIN TEXT

  C :

  1. if (web_request.user_agent_string == CRAWLER_USER_AGENT)
  2.  return cloaked_data ;
  3. else
  4.  return real_data ;

  You can verify this for yourself using the wget command line utility :

  <br />
$ wget --quiet --user-agent="<strong>Mozilla/5.0</strong>" \<br />
 http://www.archiveteam.org/index.php?title=Geocities -O - | grep \&lt;title\&gt;<br />
&lt;title&gt;GeoCities - Archiveteam&lt;/title&gt;

  $ wget —quiet —user-agent="Googlebot/2.1"
  http://www.archiveteam.org/index.php?title=Geocities -O - | grep \<title\>
  <title>Cheap xanax | Online Drug Store, Big Discounts</title>
  

  I guess the little web prank worked because the phaux-pharma stuff got indexed. It makes we wonder if there’s a MediaWiki plugin that does this automatically.

  For extra fun, here’s a site called the CloakingDetector which purports to be able to detect whether a page employs cloaking. This is just one humble observer’s opinion, but I don’t think the site works too well :