Re: reword documentation about symbol stripping

2010-11-23 Thread MK
On Tue, 23 Nov 2010 01:42:07 GMT k...@freefriends.org (Karl Berry) wrote: > it addresses an issue that > some people may not know about, so maybe it would be good to > briefly explain further? > > I agree, thanks. I changed the text to look like this: > > By default, the Make rules sho

Re: reword documentation about symbol stripping (was: default -g ??!?)

2010-11-21 Thread MK
On Sun, 21 Nov 2010 17:44:10 +0100 Ralf Wildenhues wrote: > Oh well. This thread has been so noisy and unproductive, maybe we > should seize the opportunity to take a bit of good away from it. > > Karl, what do you think about this rewording (against the gnulib copy > of make-stds.texi) that mak

Re: default -g ??!?

2010-11-21 Thread MK
On Sun, 21 Nov 2010 10:07:31 +0900 Miles Bader wrote: > MK writes: > > If you say so, then I guess I am imagining things ;) I have never > > given the issue much thought until now, I suppose I need to do a bit > > more research on the issue. > > Indeed, it&#x

Re: default -g ??!?

2010-11-20 Thread MK
On Sat, 20 Nov 2010 14:21:27 -0600 (CST) Bob Friesenhahn wrote: > Under a normal operating system (i.e. perhaps not Plan 9, I am not > sure) the debug symbols are separate from the executable text so that > the OS will never read the debug symbol area while it is loading the > program. This m

Re: default -g ??!?

2010-11-20 Thread MK
t or yum, but for some particular things like this (or for projects such as my own, which are not available as binaries for every distro), I source build. Also, if you are using a small or offbeat linux distribution, there's surely a lot of software that simply is not available for it in binary,

Re: default -g ??!?

2010-11-20 Thread MK
Note that > this is not unique to Debian; Okay, so to stretch the analogy: one imperialist nation follows the example of another, so this justifies it? Methinks "the emperor wears no clothes" here. MK -- "The angel of history[...]is turned toward the past." (Walter Benjamin)

Re: default -g ??!?

2010-11-20 Thread MK
to kowtow to a "Goliath rules David" type extortion whereby the distros say, your default build *must* contain debugging symbols. I suppose that might mean having to maintain a slightly different package just for them; no big deal, but still I think a poor compromise consequential of bad policy. MK -- "The angel of history[...]is turned toward the past." (Walter Benjamin)

Re: default -g ??!?

2010-11-20 Thread MK
On Sat, 20 Nov 2010 16:51:48 +0100 Ralf Wildenhues wrote: > > > Maybe there is a way to do this via autoconf? > > > > Yes, you can place: > > > > CFLAGS="" > > > > at the beginning of your configure.ac, after AM_INIT_AUTOMAKE but > > before AC_PROG_CC. > > > > This will prevent your configur

Re: default -g ??!?

2010-11-20 Thread MK
On Sat, 20 Nov 2010 10:36:34 -0500 MK wrote: > If and when you do need debugging symbols, it should be easy to opt > *for* them. Instead, I am left with the choice of leaving them in by > default, or having to use "strip", making it impossible to add them. Sorry if that

Re: default -g ??!?

2010-11-20 Thread MK
Ah, it's because of GNU make: "By default, the Make rules should compile and link with -g, so that executable programs have debugging symbols. Users who don't mind being helpless can strip the executables later if they wish." Nice, flexible software it ain't. This is an assbackward policy. Th

Re: default -g ??!?

2010-11-20 Thread MK
On Sat, 20 Nov 2010 15:31:01 +0100 Ralf Wildenhues wrote: > Hello, > > * MK wrote on Fri, Nov 19, 2010 at 08:10:25PM CET: > > Since I could not find a way to prevent the project being built -g, > > and there is no need for this. > > ./configure CFLAGS=-O2 That do

default -g ??!?

2010-11-20 Thread MK
e and my packager at debian is now saying they do not want strip used in makefiles. How can I prevent -g from being used? MK -- "The angel of history[...]is turned toward the past." (Walter Benjamin)