Re: -msg_* flags for cc on osf

[Peter O'Gorman]

On Fri, 2007-07-06 at 17:05 +0200, Ralf Wildenhues wrote:
> Hello Peter,
> 
> * Peter O'Gorman wrote on Fri, Jul 06, 2007 at 04:47:42PM CEST:
> > 
> > In my opinion, unless there is a system where this patch would cause
> > issues, it is much more convenient for users to not have to bracket
> > their compiler flags with -Xcompiler.
> 
> Well I checked now.  You can't allow through -msg* because the system
> that you would break would be just this very compiler: 4.0D's cc has
>   -msg_dump
> which takes no argument.  Tru 64 5.1's cxx also has
>   -msg_quiet
>   -msg_display_number
>   -msg_display_tag

Hi Ralf,

I think you are misreading the patch. Right now, libtool allows any flag
starting with -m through to the linker. The issue that Bob encountered
was that the -msg_disable flag was being sent to the linker, but its
argument was not. The patch *stops* flags starting with -msg_ from
getting passed to the linker when creating a shared library. It has
nothing to do with the arguments really.

I'm not that attached to it though, and will be happy to change :-)

Peter