Re: term, utf-8 and cooked mode, combining characters

2002-09-17 Thread Roland McGrath
readline would need some work to have a different backend hooking into the term bottom half instead of the POSIX termios world it's written for. I fear it's also kind of big to have in term, and I worry it might not be as robust in all ways we would want term to be. The real reason to use readli

-std=gnu99 fixes

2002-09-17 Thread Marcus Brinkmann
Hi, I tested moving -std=gnu99 to CFLAGS rather than CPPFLAGS and it works just fine, so I committed the changes. I also removed the (spinlock_t) in the compound literal, so that it is recognized as a constant by gcc. This fixes the -std=gnu99 compile for me. Thanks, Marcus -- `Rhubarb is no

Bug#161231: crash server crashing

2002-09-17 Thread Roland McGrath
> The crash server is crashing. I have seen the following assertion > triggered: > > crash: ../../exec/elfcore.c:55: fetch_thread_regset: Assertion > `sizeof (struct i386_thread_state) == sizeof (prgrset_t)' failed. D'oh. That's a compile-time constant crash. Clearly noone has tried this

Bug#161231: crash server crashing

2002-09-17 Thread Neal H. Walfield
Package: Hurd Version: 20020804-1 The crash server is crashing. I have seen the following assertion triggered: crash: ../../exec/elfcore.c:55: fetch_thread_regset: Assertion `sizeof (struct i386_thread_state) == sizeof (prgrset_t)' failed. That is, compile: #include int main (void) {

Re: preprocessor/7947: cpp0 -std=gnu99 rejects # comments

2002-09-17 Thread Marcus Brinkmann
On Tue, Sep 17, 2002 at 01:00:02PM -0700, Jeff Bailey wrote: > On Tue, Sep 17, 2002 at 09:45:09PM +0200, Marcus Brinkmann wrote: > > > Ayup, I just see my mistake. We are setting -std=gnu99 in CPPFLAGS, > > not CFLAGS. D'oh! I will put the blame elsewhere then :) > > CFLAGS is certainly the w

Re: preprocessor/7947: cpp0 -std=gnu99 rejects # comments

2002-09-17 Thread Jeff Bailey
**Pruning CC: list to bug-hurd** On Tue, Sep 17, 2002 at 09:45:09PM +0200, Marcus Brinkmann wrote: > Ayup, I just see my mistake. We are setting -std=gnu99 in CPPFLAGS, > not CFLAGS. D'oh! I will put the blame elsewhere then :) CFLAGS is certainly the wrong place for this, because it's requi

Re: preprocessor/7947: cpp0 -std=gnu99 rejects # comments

2002-09-17 Thread Marcus Brinkmann
On Tue, Sep 17, 2002 at 08:22:38PM +0100, Neil Booth wrote: > Marcus Brinkmann wrote:- > > > That is my fault for not being precise enough in my bug report, sorry. > > > > The problem is that gcc calls the preprocessor with this ordering when > > compiling an assembler file (foo.S) with the -std

Re: preprocessor/7947: cpp0 -std=gnu99 rejects # comments

2002-09-17 Thread Neil Booth
Marcus Brinkmann wrote:- > That is my fault for not being precise enough in my bug report, sorry. > > The problem is that gcc calls the preprocessor with this ordering when > compiling an assembler file (foo.S) with the -std=gnu99 option. > > Try "echo \# foo > foo.S" and "gcc -std=gnu99 -o foo

Re: preprocessor/7947: cpp0 -std=gnu99 rejects # comments

2002-09-17 Thread Marcus Brinkmann
I have no idea if just replying to this works, with all those CC's, but I hope for the best. On Tue, Sep 17, 2002 at 06:22:20PM -, [EMAIL PROTECTED] wrote: > Synopsis: cpp0 -std=gnu99 rejects # comments > > State-Changed-From-To: open->closed > State-Changed-By: neil > State-Changed-When: Tu

Re: preprocessor/7947: cpp0 -std=gnu99 rejects # comments

2002-09-17 Thread neil
Synopsis: cpp0 -std=gnu99 rejects # comments State-Changed-From-To: open->closed State-Changed-By: neil State-Changed-When: Tue Sep 17 11:22:20 2002 State-Changed-Why: Not a bug: -std=gnu99 overrides -lang-asm as it comes later; it contains an implicit -lang-c. You might get away

Re: c/7946: -std=gnu99 and casted empty srtuct initializers

2002-09-17 Thread jsm28
Synopsis: -std=gnu99 and casted empty srtuct initializers State-Changed-From-To: open->closed State-Changed-By: jsm28 State-Changed-When: Tue Sep 17 08:24:50 2002 State-Changed-Why: This is deliberate. C99 compound literals are not constant expressions but unnamed variables intitialized

Re: Can't build current hurd CVS tree -- error from skbuff.c

2002-09-17 Thread Marcus Brinkmann
On Fri, Sep 13, 2002 at 11:22:17AM -0400, David Walter wrote: > > - > > linux-src/net/core/skbuff.c:67: initializer element is not constant > > - > > I encounter

Re: Can't build current hurd CVS tree -- error from skbuff.c

2002-09-17 Thread Marcus Brinkmann
On Fri, Sep 13, 2002 at 11:22:17AM -0400, David Walter wrote: > > - > > linux-src/net/core/skbuff.c:67: initializer element is not constant > > - > > I encounter

cpp0 -std=gnu99 rejects # comments

2002-09-17 Thread marcus
>Category: preprocessor >Synopsis: cpp0 -std=gnu99 rejects # comments >Confidential: no >Severity: serious >Priority: medium >Class: rejects-legal >Submitter-Id: net >Originator: Marcus Brinkmann >Release:gcc (GCC) 3.2 (20020809) Debian prerelease >

-std=gnu99 and casted empty srtuct initializers

2002-09-17 Thread marcus
>Category: c >Synopsis: -std=gnu99 and casted empty srtuct initializers >Confidential: no >Severity: serious >Priority: medium >Class: rejects-legal >Submitter-Id: net >Originator: Marcus Brinkmann >Release:gcc (GCC) 3.2 (20020809) Debian prerelease

Re: OSKit mach w/St Pats

2002-09-17 Thread Michal 'hramrach' Suchanek
On Sat, Sep 14, 2002 at 12:04:41AM +0200, Joachim Nilsson wrote: > OSKIT_LIBDIR=/usr/local/lib/oskit \ It looks like this: you install oskit into $prefix (=/usr/local) and the libs go to $prefix/lib (=/usr/local/lib) and you set OSKIT_LIBDIR to $prefix/lib/oskit (=/usr/local/lib/oskit). Is this