On Thu, 6 Mar 2014 12:16:09 +0100, Diego Biurrun <[email protected]> wrote: > On Thu, Mar 06, 2014 at 12:12:25PM +0100, Anton Khirnov wrote: > > On Thu, 6 Mar 2014 12:06:44 +0100, Diego Biurrun <[email protected]> wrote: > > > On Thu, Mar 06, 2014 at 09:24:13AM +0100, Anton Khirnov wrote: > > > > --- /dev/null > > > > +++ b/compat/float/float.h > > > > @@ -0,0 +1,35 @@ > > > > + * You should have received a copy of the GNU Lesser General Public > > > > + * License along with Libav; if not, write to the Free Software > > > > + * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA > > > > 02110-1301 USA > > > > + */ > > > > + > > > > +#include_next <float.h> > > > > + > > > > --- /dev/null > > > > +++ b/compat/float/limits.h > > > > @@ -0,0 +1,22 @@ > > > > + * You should have received a copy of the GNU Lesser General Public > > > > + * License along with Libav; if not, write to the Free Software > > > > + * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA > > > > 02110-1301 USA > > > > + */ > > > > + > > > > +#include_next <limits.h> > > > > > > These two are missing multiple inclusion guards. > > > > That is intentional, since we do not know in what order will the headers be > > included and we always want our values to be defined last > > How do you ensure that our values come last? >
Don't quite understand the question. Just look at the patch. -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
