Re: Building for release or debug

[Robert E. Griffith]

Thanks Chet and Jeff, now I am understanding better. Its been a decade 
or two since I programmed in C and never with gnu standards. I was 
afraid that if I started overriding CFLAGS on the make cmd it would 
remove some required options but now I see its quite simple.

Using  -g with no -O made it so I could see all my variables and found 
the bug in no time.

--BobG


On 5/10/22 20:54, Jeffrey Walton wrote:
> On Tue, May 10, 2022 at 4:29 PM Chet Ramey <chet.ramey@case.edu> wrote:
> > On 5/10/22 9:42 AM, Robert E. Griffith wrote:
> > > ...
> > > On a different but related note, when I build my loadable builtin against
> > > the headers and loadables/makefile.inc from the ubuntu bash-builtin
> > > package. I still get symbols in my .so. Is there an option that I can
> > > specify to make that will build a release version?
> > So by a `release' version you mean a version without symbols? Use CFLAGS.
> > If you want to strip as many debugging symbols as you can, use
> > CFLAGS="-O2 -s" -- which might be overkill for a shared object -- or look
> > at some of the options to `strip'.
> The install-strip recipe might also work for Robert. See
> https://www.gnu.org/prep/standards/standards.html#Standard-Targets
>
> Jeff