with __attribute__((always_inline)) declarations.
This fixes the build on Mac OS X 10.4.11.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@27485 b3059339-0415-0410-9bf9-f77b7e298cf2
The original problem was that FSF and Apple gcc used a different syntax
for vector declarations, i.e. {} vs. (). Nowadays Apple gcc versions support
the standard {} syntax and versions that support {} are available on all
relevant Mac OS X versions. Thus the greater compatibility is no longer
worth cluttering the code with macros.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@27350 b3059339-0415-0410-9bf9-f77b7e298cf2
It have been broken since API changes in liba52-0.7.4
that have been introduced with commit r18723.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@25514 b3059339-0415-0410-9bf9-f77b7e298cf2
compare.c:18: warning: implicit declaration of function ‘exit’
compare.c:18: warning: incompatible implicit declaration of built-in function ‘exit’
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@25503 b3059339-0415-0410-9bf9-f77b7e298cf2
set by configure instead of an OS-specific directive when #including altivec.h.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@25356 b3059339-0415-0410-9bf9-f77b7e298cf2
The macro definition depends on compiler capabilities, not OS features.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@25355 b3059339-0415-0410-9bf9-f77b7e298cf2
between common, MPlayer-specific and MEncoder-specific parts.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@22546 b3059339-0415-0410-9bf9-f77b7e298cf2
Patch by Emanuele Giaquinta % e P giaquinta A glauco P it %
Original thread:
Subject: [MPlayer-dev-eng] [PATCH] liba52/parse.c: avoid dirty hack on mingw32
Date: 10/25/2006 03:19 AM
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@20779 b3059339-0415-0410-9bf9-f77b7e298cf2
header files that happen to have the same name as internal ones.
based on a patch by Vladislav Naumov, vladislav.naumov **at** gmail **dot** com
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@19426 b3059339-0415-0410-9bf9-f77b7e298cf2
patch replaces '()' for the correct '(void)' in function
declarations/prototypes which have no parameters. The '()' syntax tell
thats there is a variable list of arguments, so that the compiler cannot
check this. The extra CFLAG '-Wstrict-declarations' shows those cases.
Comments about a similar patch applied to ffmpeg:
That in C++ these mean the same, but in ANSI C the semantics are
different; function() is an (obsolete) K&R C style forward declaration,
it basically means that the function can have any number and any types
of parameters, effectively completely preventing the compiler from doing
any sort of type checking. -- Erik Slagter
Defining functions with unspecified arguments is allowed but bad.
With arguments unspecified the compiler can't report an error/warning
if the function is called with incorrect arguments. -- Måns Rullgård
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@17567 b3059339-0415-0410-9bf9-f77b7e298cf2
