Hi Stepan,
* Stepan Kasal wrote on Tue, May 31, 2005 at 08:30:03PM CEST:
On Tue, May 31, 2005 at 05:27:08PM +0200, Ralf Wildenhues wrote:
Note also that some compilers won't error out on unknown flags (esp
Intel ones :) but only issue a warning. This may or may not matter for
you. If it
* J.T. Conklin wrote on Tue, May 31, 2005 at 08:37:44PM CEST:
Ralf Wildenhues [EMAIL PROTECTED] writes:
* J.T. Conklin wrote on Sun, May 29, 2005 at 07:34:46PM CEST:
Does anyone have a macro for testing gcc's symbol visibility options
(-fvisibility=hidden, etc.)? The ACE/TAO autoconf
* J.T. Conklin wrote on Sun, May 29, 2005 at 07:34:46PM CEST:
Does anyone have a macro for testing gcc's symbol visibility options
(-fvisibility=hidden, etc.)? The ACE/TAO autoconf scripts currently
checks for gcc/g++ = 4.0, but that loses on non-ELF targets.
I believe some Intel compilers
Hi,
On Tue, May 31, 2005 at 05:27:08PM +0200, Ralf Wildenhues wrote:
Note also that some compilers won't error out on unknown flags (esp
Intel ones :) but only issue a warning. This may or may not matter for
you. If it does: For example, Libtool-1.5.18 employs some trickery to
find out the
Does anyone have a macro for testing gcc's symbol visibility options
(-fvisibility=hidden, etc.)? The ACE/TAO autoconf scripts currently
checks for gcc/g++ = 4.0, but that loses on non-ELF targets.
--jtc
--
J.T. Conklin
___
Autoconf mailing
