RE: [AD] Fortify and Allegro

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]

To: "'alleg-developers@xxxxxxxxxx'" <alleg-developers@xxxxxxxxxx>
Subject: RE: [AD] Fortify and Allegro
From: Vincent Penquerc'h <Vincent.Penquerch@xxxxxxxxxx>
Date: Wed, 28 May 2003 14:12:58 +0100

Title: RE: [AD] Fortify and Allegro

> It's not counterintuitive, it's simply broken: you can't
> silently discard a
> configure option without telling the user.

Hmm, well...
either --enable-debug-with-fortify, as you said,
or --enable-fortify-for-debug-library-if-it-is-actually-requested.
Or --enable-fortify affects all selected targets (that one would
be the cleanest, but would be a bit pointless I think).

If going for --enable-debug-with-fortify, what if --enable-debug
is also given ? Shall we rename --enable-debug to
--enable-debug-without-fortify ?

--
Vincent Penquerc'h

Follow-Ups:
- Re: [AD] Fortify and Allegro
  - From: Eric Botcazou
- Re: [AD] Fortify and Allegro
  - From: Hein Zelle

Messages sorted by: [ date | thread ]
Prev by Date: Re: [AD] grabber patch to replace an object
Next by Date: Re: [AD] Fortify and Allegro
Previous by thread: Re: [AD] Fortify and Allegro
Next by thread: Re: [AD] Fortify and Allegro

Mail converted by MHonArc 2.6.19+

http://listengine.tuxfamily.org/