| |||||||||||||
Security implications for user interface changes!Security implications for user interface changes!Posted Dec 18, 2012 20:14 UTC (Tue) by nix (subscriber, #2304)In reply to: Security implications for user interface changes! by mirabilos Parent article: Security implications for user interface changes?
Uuuuh... yeah, when you generate configure, you *do* need binaries to do it. You need binaries of the shell tools and a working sed as well as GNU m4. Why is GNU m4 so bad, yet a working sed not a problem? (Note that a lot of otherwise Unixlike operating systems don't ship a working sed, just as they don't ship a working m4.)
If your model depends on generating configure on every build platform, your model is *broken*. That's not how configure is meant to work. Generate once -- run everywhere.
(Log in to post comments)
Security implications for user interface changes! Posted Dec 18, 2012 20:38 UTC (Tue) by mirabilos (subscriber, #84359) [Link]
We have a working sed *and* a working m4 on all platforms.
They’re just usually the BSD variants, not the GNU variants.
In fact, all target platforms (Interix to the lowest degree)
That model is *not* broken, and has worked with GNU tools for
|
|||||||||||||