> Is there any reasonable way to to issue a #warning if something uses
> that, but permit the compile to continue?
Not for a compile-time constant (unless there is some new cpp feature in
gcc that I don't know about). GNU ld's symbol warnings provide a way to do
that at link time for symbols (g
> Even though so many applications depend on MAXPATHLEN, why doesn't
> Hurd define it as an arbitrary number (e.g. INT_MAX)?
The way that most programs use MAXPATHLEN is as the size statically-sized
arrays, so an unreasonably large value will either just not work or will
eat unreasonable amount
On Sat, Sep 30, 2000 at 04:07:04AM +0900, OKUJI Yoshinori wrote:
> Even though so many applications depend on MAXPATHLEN, why doesn't
> Hurd define it as an arbitrary number (e.g. INT_MAX)?
Is there any reasonable way to to issue a #warning if something uses
that, but permit the compile to con
Even though so many applications depend on MAXPATHLEN, why doesn't
Hurd define it as an arbitrary number (e.g. INT_MAX)?
Okuji
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Hi,
I just fixed a relevant bug in gnumach:
2000-09-29 Marcus Brinkmann <[EMAIL PROTECTED]>
* i386/i386at/conf.c (dev_name_list): Don't use MACH_COM to check
if com support is enabled, but NCOM, as it used to be.
Com support was added in gnumach by default, but did not get an
