Recherche avancée

Médias (0)

Mot : - Tags -/serveur

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (60)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    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 (...)

Sur d’autres sites (4635)

  • Compiling ffmpeg : how to force it to link to a specific libx264 ?

    29 août 2012, par PaulJ

    I'm trying to compile the newest version of ffmpeg (in CentOS 5.3). I first downloaded the latest version of libx264, compiled it with --enable-static and installed it in /usr/local/. However, when I then compile ffmpeg I get this error message :

    libavcodec/libavcodec.a(libx264.o): In function `X264_init':
    
/usr/local/src/ffmpeg/libavcodec/libx264.c:494: undefined reference to `x264_encoder_open_125'
    
collect2: ld returned 1 exit status
    
make: *** [ffmpeg_g] Error 1

    Searching on the net, I see that this can happen if ffmpeg is picking up an older version of libx264, which I indeed have (in /usr/lib) and can't uninstall because other pieces of software depend on it. The question is then : how can I force ffmpeg to link against the libx264 that I want ? The last time I had to do this (admittedly a year ago) I also had 2 versions of libx264, and I don't remember having to do anything special. Is there a configure switch that I'm forgetting ?

  • avcodec/adpcm : use assert for codec id instead or error return

    31 décembre 2018, par Michael Niedermayer
    avcodec/adpcm : use assert for codec id instead or error return

    A unsupported codec_id is a internal error and should not happen
    

    Reviewed-by : Paul B Mahol <onemda@gmail.com>
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavcodec/adpcm.c

  • http: avoid out of bound accesses on broken Set-Cookie headers

    8 mars 2018, par wm4
    http: avoid out of bound accesses on broken Set-Cookie headers

    It's trivial to craft a HTTP response that will make the code for
    
skipping trailing whitespace access and possibly overwrite bytes outside
    
of the memory allocation. Why this can happen is blindingly obvious : it
    
accesses cstr[strlen(cstr)-1] without checking whether the string is
    
empty.
    • [DH] libavformat/http.c

Navigation