1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
This is a recopilation of common porting problems and their solutions. It takes information from:
<http://www.debian.org/ports/hurd/hurd-devel-debian/>
<http://hurd.dyndns.org/> (not yet, because it's down atm)
and other misc sources.
First of all, see [BtsFiling](http://www.vmlinux.org/twikihttp://LOCATIONHurd/BtsFiling) if you need instructions on manipulating [Debian](http://www.debian.org/) source packages and submitting patches to their [Bug Tracking System](http://bugs.debian.org/).
\* Missing pthreads
Nothing. We don't have pthreads yet (It's being worked on).
\* Undefined PIPE\_BUF
Change it to use sysconf(\_SC\_PIPE\_BUF) #ifndef PIPE\_BUF. (from a Roland [[McGrath]] message in debian-hurd)
\* Bad File Descriptor
If you get Bad File Descriptor error when trying to read from a file (or accessing it at all), check the open() invocation. The second argument is the access method. If it is a hard coded number instead of a symbol defined in the standard header files, the code is screwed and should be fixed to either use O\_RDONLY, O\_WRONLY or O\_RDWR. This bug was observed in the fortunes and mtools packages for example.
\* PATH\_MAX
Every unconditionalized use of PATH\_MAX is a POSIX incompatibility. If there is no upper limit on the length of a path, this symbol is not defined in any header file. Instead, you need to either use a different implementation that does not rely on the length of a string or use sysconf() to query the length at runtime. If sysconf() returns -1, you have to use realloc() to allocate the needed memory dynamically.
\* MAXHOSTNAMELEN
see PATH\_MAX
\* MAXPATHLEN
see PATH\_MAX
\* NOFILE
Replace with RLIMIT\_NOFILE
\* GNU specific #define
If you need to include specific code for the Hurd using #if...#endif, then you can use the **_GNU_** symbol to do so. But think (at least) thrice! before doing so. In most situations, this is completely unnecessary and will create more problems than it may solve. Better ask on the mailing list how to do it right if you can't think of a better solution.
\* sys\_errlist[] vs. strerror()
If a program has only support for sys\_errlist[] you will have to do some work to make it compile on the Hurd, which has dropped support for it and does only provide strerror(). Steinar Hamre writes about strerror():
strerror() should be used because: o It is the modern, POSIX way. o It is localized. o It handles invalid signals/numbers out of range. (better errorhandling and not a buffer-overflow-candidate/security risk)
strerror() should always be used if it is available. Unfortunaly there are still some old non-POSIX systems that do not have strerror(), only sys\_errlist[].
Today, only supporting strerror() is far better than only supporting sys\_errlist[]. The best (from a portability viewpoint), however is supporting both. For configure.in, you will need:
AC\_CHECK\_FUNCS(strerror)
To config.h.in, you need to add:
#undef HAVE\_STRERROR
Then something like:
#ifndef HAVE\_STRERROR static char \* private\_strerror (errnum) int errnum; \{ extern char \*sys\_errlist[]; extern int sys\_nerr;
if (errnum > 0 && errnum <= sys\_nerr) return sys\_errlist[errnum]; return "Unknown system error"; \} #define strerror private\_strerror #endif /\* HAVE\_STRERROR \*/
You can for example look in the latest fileutils (the above is a simplified version of what I found there.) Patches should of course be sent to upstream maintainers, this is very useful even for systems with a working sys\_errlist[].
Of course, if you don't care about broken systems (like MS-DOG) not supporting strerror() you can just replace sys\_errlist[] directly (upstream might not accept your patch, but debian should have no problem)
\* Filenames ending in a slash \`/'
Those are evil if they don't exist and you want to name a directory this way. For example, mkdir foobar/ will not work on the Hurd. This is POSIX compatible. POSIX says that the path of a directory may have slashes appended to it. But the directory does not exist yet, so the path does not refer to a directory, and hence trailing slashes are not guaranteed to work. Just drop the slashes, and you're fine.
-- [[Main/RobertMillan]] - 22 Jul 2002
|
