Recherche avancée

Médias (3)

Mot : - Tags -/collection

Autres articles (28)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Pas question de marché, de cloud etc...

    10 avril 2011

    Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
    sur le web 2.0 et dans les entreprises qui en vivent.
    Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
    Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
    le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
    Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)

Sur d’autres sites (4892)

  • Revision 4674312382 : Merge "Code cleanup." into experimental

    21 février 2013, par John Koleszar

    Merge "Code cleanup." into experimental

  • Revision 8c16dee4f2 : Merge "Remove "eobs" array in MACROBLOCKD." into experimental

    21 février 2013, par Ronald S. Bultje

    Merge "Remove "eobs" array in MACROBLOCKD." into experimental

  • NDK r8c warning for asm objects regarding "Cortex-A8 erratum" - should I be worried ?

    7 décembre 2012, par Alex Cohn

    Question : What is the meaning of this warning ? If there are no real-life consequences, I can live with it for a while... But I am concerned with what will happen if our program gets loaded on one of the faulty chips.

    Background : With NDK r8c, linking of X264 encoder issues warnings :

    cannot scan executable section 1 of libx264.a(dct-a.o) for Cortex-A8 erratum because it has no mapping symbols

    ... same warning for all assembly files in libx264.

    libx264.a itself was cross-compiled on the same machine with the same 4.6 toolchain taken from NDK.

    Here are the instructions to easily reproduce the problem (Ubuntu or MacOS) :

    1. Download x264-snapshot-20121203-2245 from ftp://ftp.videolan.org/pub/x264/snapshots/last_x264.tar.bz2

    2. Run ./configure --enable-pic --enable-strip --enable-static --cross-prefix=~/android-ndk-r8c/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/arm-linux-androideabi- --sysroot=~/android-ndk-r8c/platforms/android-14/arch-arm --host=arm-linux

    3. Run ~/android-ndk-r8c/prebuilt/linux-x86/bin/make

    It will build the static library, and after that display the Cortex-A8 warning while linking the x265 executable. I am not worried about the compiler warnings, because building libx264.a is done offline, it is not part of our official daily build.

    I have reported this as http://code.google.com/p/android/issues/detail?id=40794.

    I tried to add the mapping symbols manually to dct-a.S following the ARM.com instructions, but this had no effect.

Navigation