Re: [dev] [9base] troff segmentation fault.

2009-10-16 Thread Ramil Farkhshatov
On Thu, Oct 15, 2009 at 04:37:53PM -0400, Kris Maglione wrote: > Yep, you've definitely clobbered your CFLAGS, either by specifying them > on the commandline, or by not using += to define them in config.mk. Yes, I discovered that PKGBUILD I used was broken. Thanks. -- Ramil Farkhshatov

Re: [dev] [9base] troff segmentation fault.

2009-10-15 Thread Kris Maglione
On Thu, 15 Oct 2009 12:57:06 +0400 Ramil Farkhshatov wrote: > On Thu, Oct 15, 2009 at 04:30:00AM -0400, Kris Maglione wrote: > > On Wed, 14 Oct 2009 12:39:14 +0400 > > Ramil Farkhshatov wrote: > > > > > Trying to use troff from 9base, but it crashes. > > > Here is backtrace of just running trof

Re: [dev] [9base] troff segmentation fault.

2009-10-15 Thread Ramil Farkhshatov
On Thu, Oct 15, 2009 at 04:30:00AM -0400, Kris Maglione wrote: > On Wed, 14 Oct 2009 12:39:14 +0400 > Ramil Farkhshatov wrote: > > > Trying to use troff from 9base, but it crashes. > > Here is backtrace of just running troff without arguments: > > It looks like you've changed the Makefile, or so

Re: [dev] [9base] troff segmentation fault.

2009-10-15 Thread Kris Maglione
On Wed, 14 Oct 2009 12:39:14 +0400 Ramil Farkhshatov wrote: > Trying to use troff from 9base, but it crashes. > Here is backtrace of just running troff without arguments: It looks like you've changed the Makefile, or something. Please change @${CC} to ${CC} in std.mk, build just troff, and post

[dev] [9base] troff segmentation fault.

2009-10-14 Thread Ramil Farkhshatov
Trying to use troff from 9base, but it crashes. Here is backtrace of just running troff without arguments: Program received signal SIGSEGV, Segmentation fault. 0x080787ee in strncmp () #0 0x080787ee in strncmp () No symbol table info available. #1 0x0805e6e8 in unsharp (old=0x0) at unsharp.c:30