Re: __sigisempty() undefined if "cc -g" used.

2000-01-10 Thread Bruce Evans
On Mon, 10 Jan 2000, Alexander Leidinger wrote: > On 11 Jan, Bruce Evans wrote: > > >> Didn´t we have "makeoptions DEBUG=-g" as a kernel option to compile the > >> kernel with debug information? What about "config -g MYKERNEL"? > > > > DEBUG is a private variable in kernel Makefiles. "config -

Re: __sigisempty() undefined if "cc -g" used.

2000-01-10 Thread Alexander Leidinger
On 11 Jan, Bruce Evans wrote: >> Didn´t we have "makeoptions DEBUG=-g" as a kernel option to compile the >> kernel with debug information? What about "config -g MYKERNEL"? > > DEBUG is a private variable in kernel Makefiles. "config -g MYKERNEL" If I set DEBUG in make.conf it should work, righ

Re: __sigisempty() undefined if "cc -g" used.

2000-01-10 Thread Bruce Evans
On Mon, 10 Jan 2000, Alexander Leidinger wrote: > On 10 Jan, Bruce Evans wrote: > > >> Better yet: DEBUG_FLAGS=-g > > > > Except it only supported in bsd.prog.mk and bsd.lib.mk, but not in > > bsd.kmod.mk, kernel Makefiles, or if no bsd .mk files are included > > A few verbose module makefiles

Re: __sigisempty() undefined if "cc -g" used.

2000-01-10 Thread Alexander Leidinger
On 10 Jan, Bruce Evans wrote: >> Better yet: DEBUG_FLAGS=-g > > Except it only supported in bsd.prog.mk and bsd.lib.mk, but not in > bsd.kmod.mk, kernel Makefiles, or if no bsd .mk files are included > A few verbose module makefiles add it explicitly. You can also use > COPTS, but it is only su

Re: __sigisempty() undefined if "cc -g" used.

2000-01-09 Thread Bruce Evans
On Sun, 9 Jan 2000, John Polstra wrote: > In article <[EMAIL PROTECTED]>, > Bruce Evans <[EMAIL PROTECTED]> wrote: > > > > You apparently > > clobbered -O in CFLAGS by setting CFLAGS=-g. -g normally needs to be > > added to CC to avoid breaking CFLAGS (CC='cc -g'). > > Better yet: DEBUG_FLAGS

Re: __sigisempty() undefined if "cc -g" used.

2000-01-09 Thread John Polstra
In article <[EMAIL PROTECTED]>, Bruce Evans <[EMAIL PROTECTED]> wrote: > > You apparently > clobbered -O in CFLAGS by setting CFLAGS=-g. -g normally needs to be > added to CC to avoid breaking CFLAGS (CC='cc -g'). Better yet: DEBUG_FLAGS=-g John To Unsubscribe: send mail to [EMAIL PROTECTED

Re: __sigisempty() undefined if "cc -g" used.

2000-01-07 Thread Bruce Evans
On Fri, 7 Jan 2000, Luoqi Chen wrote: > > In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g > > (and later CFLAGS=-g3), but ran into linker problems as a result. > > > > blitz:~> gcc poll.c -pthread > > /usr/lib/libc_r.so: undefined reference to `__sigisempty' > > > > Ev

Re: __sigisempty() undefined if "cc -g" used.

2000-01-07 Thread Jason Evans
On Fri, Jan 07, 2000 at 07:36:11PM -0500, Luoqi Chen wrote: > > In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g > > (and later CFLAGS=-g3), but ran into linker problems as a result. > > > > blitz:~> gcc poll.c -pthread > > /usr/lib/libc_r.so: undefined reference to `__si

Re: __sigisempty() undefined if "cc -g" used.

2000-01-07 Thread Luoqi Chen
> In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g > (and later CFLAGS=-g3), but ran into linker problems as a result. > > blitz:~> gcc poll.c -pthread > /usr/lib/libc_r.so: undefined reference to `__sigisempty' > > Even the simplest of C programs will get this linker er

__sigisempty() undefined if "cc -g" used.

2000-01-07 Thread Jason Evans
In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g (and later CFLAGS=-g3), but ran into linker problems as a result. blitz:~> gcc poll.c -pthread /usr/lib/libc_r.so: undefined reference to `__sigisempty' Even the simplest of C programs will get this linker error if using t