man is broken on the hurd

2000-03-12 Thread Neal H Walfield
Hi Fabrizio, Man is broken under the hurd. When one tries to view man pages as root, man executes su with the -c option. This flag is not supported under the hurd's su. This patch will fix it to work on the hurd: --- /bin/manThu Feb 10 10:50:30 2000 +++ man Sun Mar 12 18:57:28 2000 @@ -2,

Re: further (incomplete) X patches

2000-03-12 Thread Roland McGrath
> I know, but at least for X 3.3 and earlier this seems to be the usual way. > The X sources in general are platform and not feature based. Also, the Linux > support is quite complex because it deals with libc5 and various glibc based > systems, and I better not touch it at all. It should be strai

Re: further (incomplete) X patches

2000-03-12 Thread Marcus Brinkmann
On Sun, Mar 12, 2000 at 03:04:17PM -0500, Roland McGrath wrote: > As a general rule, the same feature selections appropriate for Linux/glibc > are probably the right choices for the Hurd. As always, using #ifdef __linux__ > or #ifdef __GNU__ is the worst way to choose these things, but if that's

Re: further (incomplete) X patches

2000-03-12 Thread Roland McGrath
> here are further patches for X. I grep'd for linux and checked if all > places that also apply to the Hurd include __GNU__, too. There are some > places I didn't understand, and I welcome any help with them. I would > also appreciate it if someone could revise my changes. Here are my notes, > an

further (incomplete) X patches

2000-03-12 Thread Marcus Brinkmann
Hi, here are further patches for X. I grep'd for linux and checked if all places that also apply to the Hurd include __GNU__, too. There are some places I didn't understand, and I welcome any help with them. I would also appreciate it if someone could revise my changes. Here are my notes, and att

Bug#54148: marked as done (hurd: new gcc can't compile pfinet)

2000-03-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Mar 2000 03:56:15 -0500 with message-id <[EMAIL PROTECTED]> and subject line pfinet overhauled has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Re: Proc failure with gcc-2.95.2

2000-03-12 Thread Roland McGrath
I've fixed the bug, and a Hurd all compiled with gcc-2.95.2 now runs fine. It turns out there was no particularly interesting reason gcc-2.95.2 exposed this bug, it was just the luck of the optimizer. The bug was that in the create_startup_proc case, where allocate_proc is called with MACH_PORT_N