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.
--
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
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
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
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" == Frank A Uepping <[EMAIL PROTECTED]> writes:
[...]
Frank> (I am wondering that AM_INIT_AUTOMAKE doesn't use PACKAGE_* by default.)
`AM_INIT_AUTOMAKE([OPTIONS])'
`AM_INIT_AUTOMAKE(PACKAGE, VERSION, [NO-DEFINE])'
Runs many macros required for proper operation of the generated
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.
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
> >
7268et133d3zv39w58sj7hega10d005a2u184825yfx2x62y898ve544c3bo337l 5w422g011qy090k91219f578o1m76x96et133d3zv39w58sj7hega10d005a2u182g011qy090k91219f578o1m76x9659454i4407032bv3i6h2r601746b9zj97268 et133d3zv39w58sj7hega10d005a2u184825yfx2x62y898ve544c3bo337l5w422g011qy090k91219f578o1m76x965945 4i44
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
Sind Sie Student? Haben Sie Familie? Haben Sie Arbeit?
Verdienen Sie Genug Geld? Wissen Sie Noch Wie Lange?
***
I want to check for a kernel header file with AC_CHECK_HEADER.
E.g.:
AC_CHECK_HEADER([cdrom.h],, [AC_MSG_ERROR([cdrom.h not found])])
./configure CPPFLAGS=-I/usr/include/linux
gives me:
checking cdrom.h usability... no
checking cdrom.h presence... yes
configure: WARNING: cdrom.h: present but cannot
No one? No hint, advice or what so ever...?
Op donderdag 31 juli 2003 15:52, schreef Richard Bos:
> Hello,
>
> My next question, is about how to determine that UNIX Advisory lock can
> be used on a system. This is used in the database application that I'm
> trying to port to the autoconf. The d
Ping!
I've been paperwork-complete for quite a while. Please take a look at
my patch from January:
http://mail.gnu.org/archive/html/autoconf-patches/2003-01/msg00014.html
For notes on the patch, and ChangeLog entry, see
http://mail.gnu.org/archive/html/autoconf-patches/2003-01/msg00012.html
Alter
The AC_PROG_CC/CXX are searching for a compiler.
Will the found compiler being used to compile the feature tests?
E.g.: does AC_CHECK_HEADER(...) use the compiler determined by AC_PROG_CC?
What about when the user supplies a compiler via `./configure CC=mygcc';
is that compiler used instead of th
Is it possible to determine/get the block size that can be used by a system?
I have the information below that provides some insight, but is it possible
to obtain this information from configure?
Size of DB input buffer blocks. Normally, this is
set by indicating which machine you are on
16 matches
Mail list logo