[Openal] RE: [Openal-devel] handling of c flags in configure
buck at dirtysoft.co.uk
Mon Jan 9 07:07:55 PST 2006
On Mon, 2006-01-09 at 15:24 +0100, Sven Panne wrote:
> First of all I have to say that I didn't introduce the optimization
> flags in configure.ac myself, they were from ancient times... Given the
> complexity of modern HW and SW, I'm quite aware that choosing the "best"
> flags is next to impossible, so I'm fully in line with the current
> proposals. Let's quickly discuss the flags currently used:
Additionally, I'm not too happy about the way both the current build
systems force flags. Official slackware packages, for instance, are all
i486. Even though I specify my own CFLAGS asking for this, it always
superseded by the -march=i686 in configure. It also (appeared over the
weekend?) adds -fvisibility=hidden. This breaks gcc3 compatability,
which is the default (and ONLY) compiler for slack.
It's been awhile since I've really played with many other distros, but I
imagine forcing these flags will run into trouble with other distros'
build policies at some point. The CFLAGS really should be overridden by
any specified by the user, for that reason. Plus, it makes it a bit
easier for others to play with the flags and see what works best for
I think MPlayer does that in a nice way. If you specify your own, it
disables those the developers recommend, and tells you to not even think
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://opensource.creative.com/pipermail/openal/attachments/20060109/54603d11/attachment-0001.bin
More information about the Openal