[Openal] RE: [Openal-devel] handling of c flags in configure
prakash at punnoor.de
Mon Jan 9 07:46:00 PST 2006
Am Montag Januar 9 2006 16:07 schrieb Ioan Rogers:
> 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
I haven't checked the autotools one, but I wrote the CMake build system that
you can override OpenAL's settings, ie if you specify -march=i486 it should
be appended and thus overide other conflicting flags. If this is not the
case, please report again.
> weekend?) adds -fvisibility=hidden. This breaks gcc3 compatability,
> which is the default (and ONLY) compiler for slack.
Could you be more precise? In fact it tests whether visibility is supported
and only then activates the feature. Does this lead to compile errors or
runtime errors? Or is support falsely detected? If yes, could you try whether
CMake also detects falsely support? If no, my test in configure is not enough
and I need to check for the compiler flag, as well (as I do in CMake). If
not, I am a bit puzzled....
//\ Prakash Punnoor /\\
More information about the Openal