On Sun, Nov 28, 2010 at 02:27:51PM -0500, Andy Dougherty <doughera@lafayette.edu> wrote: > > beginning with 5.10.something, perl enforces the use of -fstack-protector, > > even when Configure was explicitly told the compiler flags, and there is > > no way to switch it off. > > I agree with your general premise that it should be possible to get > Configure to do what you need it to do in order to build perl the way you > want to build it. just saw your reply by accident (I wasn't included in your reply's address). > I should point out, however, that while it isn't easy, it is possible to > turn it off by running Configure interactively and removing it when > prompted. Yeah, or by perl -pi -e 's/...' Configure, which is wat I am doing now. > I wasn't aware that gcc might be misleading us this way. If you could > supply us with a better test program, that would be very helpful. Presumably, you would just need to run the program and if it crashes, assume -fstack-protector doesn't quite work. > > so... please please please make -fstack-protector configurable somehow, > > better yet, don't override user-specified flags and/or improve the tets > > for platform support. > > Unfortunately, other users do rely on us supplementing the user-specified > C flags, I primarily asked for a way to disable -fstack-protector. Somehow. So, which other users rely on your enforcing -fstack-protector? Is there really any platform that needs that flag? I doubt that, so that argument simply doesn't apply. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / schmorp@schmorp.de -=====/_/_//_/\_,_/ /_/\_\Thread Previous | Thread Next