From: Tony Earnshaw (tonye@ilion.nl)
Date: Wed Oct 06 1999 - 05:11:19 CDT
Sorry that this is out of thread, but I lost some of my mail and had
nothing left to reply to ...
----- Original Message -----
From: Kent Landfield <kent@landfield.com>
To: <tonye@ilion.nl>
Cc: <hypermail@rkive.landfield.com>
Sent: Monday, October 04, 1999 6:20 PM
Subject: Re: Test configure
| :( You shouldn't have to do this to get it to run on SCO Open Server
| 5.0.5 with egcs 1.1.2. Guess there's still more to do to get
configure
| to work right on that system.
| Is MAXPATHLEN in any of the include files on your system ?
in /usr/include, 'find . -exec grep MAXPATHLEN {} \; -print':
#ifndef MAXPATHLEN
#define MAXPATHLEN 1024
./sys/fs/dtfilsys.h
#define NFS_MAXPATHLEN 1024
char *srok_data; /* string (up to NFS_MAXPATHLEN bytes) */
./sys/fs/nfs/nfs.h
#define NL_MAXPATHLEN 1024
./nl_types.h
#define NL_MAXPATHLEN 1024
./xpg4plus/nl_types.h
#define NL_MAXPATHLEN 1024
./xpg4/nl_types.h
#define NL_MAXPATHLEN 1024
./xpg4v2/nl_types.h
#define NL_MAXPATHLEN 1024
./ods_30_compat/nl_types.h
* MAXPATHLEN comes from 4.2 param.h
#define MAXPATHLEN 1024
./arpa/ftp.h
const NFS_MAXPATHLEN = 1024;
typedef string nfspath<NFS_MAXPATHLEN>;
./rpcsvc/nfs_prot.x
In limits.h, an explanation also given in diverse other headers:
/*
* The following are not defined since the value can vary according
* to the file referred to.
*
* In all cases, pathconf should be checked to find the actual value for
* a particular file.
*
* LINK_MAX _PC_LINK_MAX _POSIX_LINK_MAX
* NAME_MAX _PC_NAME_MAX PATHSIZE
* PATH_MAX _PC_PATH_MAX PATHSIZE
* PIPE_BUF _PC_PIPE_BUF _POSIX_PIPE_BUF
*
* A similar rationale applies to the following cross compatibility
values.
*
* MAXPATHLEN (from 4.2 BSD params.h)
*/
Tony
************* THE NEW DIMENSION IN DISTRIBUTION ***********
ilion Faculty B.V.
Tony Earnshaw email: tonye@ilion.nl
Randstad 21-57
1314 BH Almere-Stad tel: +31 (0) 36 548 50 10
The Netherlands fax: +31 (0) 36 534 05 34
***************** http://www.ilion.nl *********************