-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 14 October 2002 10:17, Keith Robinson wrote:
> On Mon, Oct 14, 2002 at 09:11:41PM -0600, Aaron J. Seigo wrote:
> > or you can hand hack the Makefile, as you appear to have attempted. the
> > CC= line is often, but not always, what ends up getting used. you may
> > need to do a search in the file for where "gcc" appears and append a -g
> > to it at each location. also remember that you will need to do this for
> > each Makefile in each subdirectory, if there are any. which is why doing
> > it w/configure is so much nicer =)
>
> ah, i didn't think of that. looks like a job for sed.
indeed. or perl =)
perl -pi -e 's/gcc/gcc -g/g' `tree -if | grep Makefile`
and then hope that there aren't any occurances of gcc that aren't references
to the compiler ;-)
- --
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
"Everything should be made as simple as possible, but not simpler"
- Albert Einstein
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9q78y1rcusafx20MRAmwtAJ9MWDZ1ysNvJvcjqJ+0bB5q0kNTxwCffbaZ
Fz+6ELRoDGcKh3mgIXNYmJE=
=paQR
-----END PGP SIGNATURE-----
