On 08/07/2008, Diego Biurrun <[EMAIL PROTECTED]> wrote: > On Tue, Jul 08, 2008 at 12:29:13PM +0200, Michal Suchanek wrote: > > On 07/07/2008, Diego Biurrun <[EMAIL PROTECTED]> wrote: > > > On Mon, Jul 07, 2008 at 02:48:55PM +0200, A Mennucc wrote: > > > > On Mon, Jul 07, 2008 at 10:41:46AM +0200, Michal Suchanek wrote: > > > > > On 06/07/2008, A Mennucc <[EMAIL PROTECTED]> wrote: > > > > > > also, it is compiled using --enable-debug, so it has -O2 instead > > > > > > of -O4 > > > > > > > > The reason I did that was that I was expecting some mess when > > > > I finally would have prepared a version of MPlayer linked > > > > to external FFMpeg, so a -dbg package would have helped; > > > > (and indeed a lot of mess happened) > > > > > > > > MPlayer 1.0~rc2-15 is compiled with "-g -O2" instead > > > > of "-O4 -ffast-math ....". > > > > > > > > I could reverse this flag now; but note that > > > > this flag affects the code of MPlayer itself, not the code in > > > > the FFmpeg external libraries (that are out of my reach), > > > > and AFAIK that code is much more relevant to speed. > > > > > > I would suggest that you build with the same flags that we use upstream. > > > > What are these? > > > Whatever the configure script sets; -O4 and no -g IIRC.
I guess the key is -fomit-frame-pointer to be able to build at all. The package I tried to build is broken: it sets CFLAGS:=-O2 which does not allow building mplayer at all. The line should read CFLAGS:= to remove the dpkg-buildpackage default flags and restore the mplayer default flags. > > > > I wonder how do the dpkg-buildpackage default flags > > interact with the mplayer build. > > > MPlayer's configure reacts to the CFLAGS environment variable. Yes, and dpkg-buildpackage sets that to -O2 -g if unset, and then the package rules file can change that. The joys of using packaging tools... Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
