[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
-msg_* flags for cc on osf
From: |
Peter O'Gorman |
Subject: |
-msg_* flags for cc on osf |
Date: |
Thu, 05 Jul 2007 22:06:18 -0500 |
Hi,
Bob wanted to add -msg_disable badboundchk,unusedincl to his CFLAGS on
Tru64 5.1 using the native compiler, there was a problem though. We have
a rule that lets all, otherwise unknown flags beginning with -m through
to the linker. However, we don't expect -mfoo to have an argument, so we
do not let through the argument. This results in a link error for Bob.
This patch lets libtool know about all flags beginning with -msg_ and
says to not pass them through to the linker.
There are some questions, do any other compilers use flags beginning
with -msg_ that do not take an argument and that need to be passed
through to the linker? If that is the case then this patch is wrong. I
think, however, that since we pass -m* through we should take the chance
on this, rather than staying with the status-quo on the off-chance that
there might be a system somewhere that requires -msg_something being
passed to the linker.
I won't apply this without explicit approval from someone !Bob (sorry
Bob).
Thoughts? Are there any real systems that this would break?
Peter
msg_.patch
Description: Text Data
- -msg_* flags for cc on osf,
Peter O'Gorman <=
Re: -msg_* flags for cc on osf, Bob Friesenhahn, 2007/07/06