On Fri, 2003-08-01 at 17:40, Frank A. Uepping wrote:
> I want CXXFLAGS without the -g flag BY DEFAULT!
> Because the normal user doesn't want a bloat bin with debug information.
Normal users aren't going to care. And for users who do care, there is
the "install-strip" make target.
--
Braden McD
On Saturday 02 August 2003 07:46, Richard Bos wrote:
> Op vrijdag 1 augustus 2003 21:38, schreef Frank A. Uepping:
> > Unfortuantely AC_PROG_CXX includes the `-g' option in CXXFLAGS,
> > with what I am not happy with.
> > How can I get rid of the `-g' flag in a way that doesn't *clobber* a user
> >
Braden McDaniel wrote:
On Fri, 2003-08-01 at 23:44, Harlan Stenn wrote:
It's not that hard to get rid of a flag.
nCFLAGS=
for i in $CFLAGS
do
case "$i" in
-g) ;;
*) nCFLAGS="$nCFLAGS $i" ;;
esac
done
CFLAGS=nCFLAGS
That will also purge -g if it was added explicitly by the user.
It's not that hard to get rid of a flag.
nCFLAGS=
for i in $CFLAGS
do
case "$i" in
-g) ;;
*) nCFLAGS="$nCFLAGS $i" ;;
esac
done
CFLAGS=nCFLAGS
Frank A. Uepping wrote:
> I want CXXFLAGS without the -g flag BY DEFAULT!
> Because the normal user doesn't want a bloat bin with debug information.
Could you be specific about your concerns? There should be no bloat
when compiled with -g. That just enables debug symbols to be present
in the dev
See:
http://mail.gnu.org/archive/html/autoconf/2003-04/msg00016.html
and the related messages for some possibly relevant discussion. That
thread is about giving libexecdir a different default, but I came away
with the general impression that it is difficult to change the default
defaults of
Op vrijdag 1 augustus 2003 21:38, schreef Frank A. Uepping:
> Unfortuantely AC_PROG_CXX includes the `-g' option in CXXFLAGS,
> with what I am not happy with.
> How can I get rid of the `-g' flag in a way that doesn't *clobber* a user
> supplied CXXFLAGS?
> (However, I assume resetting CXXFLAGS ent
On Fri, 2003-08-01 at 23:44, Harlan Stenn wrote:
> It's not that hard to get rid of a flag.
>
> nCFLAGS=
> for i in $CFLAGS
> do
>case "$i" in
> -g) ;;
> *) nCFLAGS="$nCFLAGS $i" ;;
>esac
> done
> CFLAGS=nCFLAGS
That will also purge -g if it was added explicitly by the user.
--
On 1-Aug-2003, Frank A. Uepping <[EMAIL PROTECTED]> wrote:
| I want CXXFLAGS without the -g flag BY DEFAULT!
| Because the normal user doesn't want a bloat bin with debug information.
Perhaps not, but as the maintainer of a package with the occasional
bug, it is annoying when someone reports a p
On Fri, 2003-08-01 at 15:38, Frank A. Uepping wrote:
> Unfortuantely AC_PROG_CXX includes the `-g' option in CXXFLAGS,
> with what I am not happy with.
Why not? It's there under the auspice that there's no good reason for it
not to be there.
> How can I get rid of the `-g' flag in a way that does
Frank A. Uepping wrote:
Unfortuantely AC_PROG_CXX includes the `-g' option in CXXFLAGS,
with what I am not happy with.
How can I get rid of the `-g' flag in a way that doesn't *clobber* a user
supplied CXXFLAGS?
(However, I assume resetting CXXFLAGS entirely is not wise, isn't it?)
Is there any A
Frank A. Uepping wrote:
On Friday 01 August 2003 23:25, Guido Draheim wrote:
Frank A. Uepping wrote:
Unfortuantely AC_PROG_CXX includes the `-g' option in CXXFLAGS,
with what I am not happy with.
How can I get rid of the `-g' flag in a way that doesn't *clobber* a user
supplied CXXFLAGS?
(Howev
On Friday 01 August 2003 23:25, Guido Draheim wrote:
> Frank A. Uepping wrote:
> > Unfortuantely AC_PROG_CXX includes the `-g' option in CXXFLAGS,
> > with what I am not happy with.
> > How can I get rid of the `-g' flag in a way that doesn't *clobber* a user
> > supplied CXXFLAGS?
> > (However, I
Unfortuantely AC_PROG_CXX includes the `-g' option in CXXFLAGS,
with what I am not happy with.
How can I get rid of the `-g' flag in a way that doesn't *clobber* a user
supplied CXXFLAGS?
(However, I assume resetting CXXFLAGS entirely is not wise, isn't it?)
Is there any AC_ switch for it, or do I
14 matches
Mail list logo
