summaryrefslogtreecommitdiff
path: root/community
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2009-03-28 19:53:35 +0100
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2009-03-28 19:53:35 +0100
commit91e6909a9c28b4848042d31466accea9e42b9714 (patch)
tree64890049de5f36fec90fb2bd683150cc9ac927a5 /community
parentab89786bd1a912b774a7a74562246cd663460d16 (diff)
a few more details
Diffstat (limited to 'community')
-rw-r--r--community/gsoc/project_ideas/maxpath.mdwn11
1 files changed, 7 insertions, 4 deletions
diff --git a/community/gsoc/project_ideas/maxpath.mdwn b/community/gsoc/project_ideas/maxpath.mdwn
index 797cc0dc..73d4ee75 100644
--- a/community/gsoc/project_ideas/maxpath.mdwn
+++ b/community/gsoc/project_ideas/maxpath.mdwn
@@ -28,10 +28,13 @@ There are a few hundred packages in Debian GNU/Hurd failing to build because of
this -- simply grep for the offending macros in the
[list_of_build_failures](http://unstable.buildd.net/buildd/hurd-i386_Failed.html).
-Fixing these issues usually boils down to replacing `char foo[PATH_MAX]` by
-`char *foo`, and using dynamic memory allocation. Sometimes this is tricky, but
-more often not very hard. With a bit of practice, it should be easily possible
-to fix several programs per day.
+Fixing these issues usually boils down to replacing `char foo[PATH_MAX]`
+by `char *foo`, and using dynamic memory allocation, i.e. e.g. a loop
+that tries geometrically growing sizes. Sometimes this is tricky, but
+more often not very hard. Sometimes it is even trivial because the GNU
+system has proper replacements. See the corresponding section of the
+[[Porting_issues_page|PortingIssues]] for more details. With a bit of practice,
+it should be easily possible to fix several programs per day.
The goal of this project is to fix the PATH_MAX and related problems in a
significant number of packages, and make the fixes ready for inclusion in