| Re: [AD] Fortify and Allegro | 
[ Thread Index | 
Date Index
| More lists.liballeg.org/allegro-developers Archives
] 
Vincent Penquerc'h wrote:
> > It's not counterintuitive, it's simply broken: you can't 
> > silently discard a 
> > configure option without telling the user.
I'm getting confused here. I'm assuming that using fortify without
debug mode is not of much use, right? If so, why not just
--enable-dbglib    :  does what it has always done
--enable-dbgprogs  :  likewise
--enable-fortify   :  turn on fortify if dbg has been specified for
                      lib or programs
and then yell a big fat warning at the user that
Fortify was requested without --dbglib:   not building fortified lib.
Fortify was requested without --dbgprogs: not building fortified programs.
Or just give one BIG warning and turn on both --dbglib and
--dbgprogs. If someone wants fortify, they're bound to want those
flags anyway, as far as I can tell.
Hein Zelle
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-< 
 Unix is user friendly. It's just very particular about who 
 it's friends are.
 Hein Zelle                     hein@xxxxxxxxxx
	                        http://www.icce.rug.nl/~hein
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<