Merge branch 'master' of arnebab@flubber:~wiki/wiki

3 files changed, 106 insertions, 26 deletions

diff --git a/hurd/running/debian/patch_submission.mdwn b/hurd/running/debian/patch_submission.mdwn
index 0fd73b7b..0a1bfb3f 100644
--- a/hurd/running/debian/patch_submission.mdwn
+++ b/hurd/running/debian/patch_submission.mdwn
@@ -8,29 +8,48 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
 is included in the section entitled
 [[GNU_Free_Documentation_License|/fdl]]."]]"""]]
 
-If you fixed a Debian package which FTBFS (fails to build from source), you should submit the patch so that all users can profit from your work.
-
-If it is not a Debian-specific patch, you should strongly consider submitting the patch upstream for inclusion.  This applies even more so if it is a GNU package, or otherwise frequently used package, or you know upstream anyway.
-
-If you had to change the code considerably and are not 100% sure you did not introduce a regression, or are not very experienced with these kinds of code changes, you should first submit your patch for review to the [Debian alioth patch tracker](http://alioth.debian.org/tracker/?atid=410472&group_id=30628&func=browse). 
-
-If the patch is trivial, or one of the Debian porters approved your patch for submission, submit the patch to the Debian BTS (bug tracking system).  You can either use the reportbug tool, or just simple mail.  In any case, you should follow these guidelines:
-
- 
- * The submission address is <submit@bugs.debian.org>
- * Subject/Bug title should be "(source-package): FTBFS on hurd-i386: (reason)"
- * "Severity:" should be "important", **not "serious"**
- * "Version:" should be the version of the source package in unstable
- * Add "Tags: patch"
- * Add "User: debian-hurd@lists.debian.org"
- * Add "Usertags: hurd"
-
-In the bug description, mention that the package fails to build on hurd-i386 and (if possible) quote the failure.  If possible, point to the failing build log from <http://buildd.debian-ports.org/build.php>.
-
-Then, explain the failure (Debian maintainers usually do not know much about Hurd-specific failures), and attach the patch.
+If you fixed a Debian package which *FTBFS* (fails to build from source), you
+should submit the patch so that all users can profit from your work.
+
+If it is not a Debian-specific patch, you should strongly consider submitting
+the patch upstream for inclusion.  This applies even more so if it is a GNU
+package, or otherwise frequently used package, or you know upstream anyway.
+
+If you had to change the code considerably and are not 100% sure you did not
+introduce a regression, or are not very experienced with these kinds of code
+changes, you should first submit your patch for review to the [Debian alioth
+patch
+tracker](http://alioth.debian.org/tracker/?atid=410472&group_id=30628&func=browse).
+
+If the patch is trivial, or one of the Debian porters approved your patch for
+submission, submit the patch to the Debian BTS (bug tracking system).  You can
+either use the reportbug tool, or just simple mail.  In any case, you should
+follow these guidelines:
+
+  * The submission address is <submit@bugs.debian.org>.
+  * The mail's subject (which will become the bug's title) should be
+    `SOURCE-PACKAGE: FTBFS on hurd-i386: REASON`.
+  * The first lines of the mail's body (the so-called *pseudo-header*):
+      * `Severity: important` -- not *serious*.
+      * `Version: VERSION` -- the version of the source package in unstable.
+      * `Tags: patch` -- as/if you include a ready-to-be-applied patch.
+      * `User: debian-hurd@lists.debian.org`
+      * `Usertags: hurd`
+
+In the bug description, mention that the package fails to build on hurd-i386
+and (if possible) quote the failure.  If possible, point to the failing build
+log from <http://buildd.debian-ports.org/build.php> or elsewhere.
+
+Then, explain the failure (Debian maintainers usually do not know much about
+Hurd-specific failures), and attach the patch.
 
 The patch should be in unidiff form.
 
-If the package uses a patch system, it is preferable to submit the patch in a ready to use form (e.g. as a dpatch), but this is not required. Also, try to keep the patch small, e.g. do not submit a 100k autotools diff for a one-line change in configure.in or a Makefile.am, but in this case mention that autotools need to be rerun and let the maintainer choose (you can suggest you would file a complete diff if the maintainer prefers)
+If the package uses a patch system, it is preferable to submit the patch in a
+ready-to-use form (e.g. as a *dpatch*), but this is not required.  Also, try to
+keep the patch small, e.g., do not submit a 100 KiB autotools diff for a
+one-line change in `configure.in` or a `Makefile.am`, but in this case mention
+that autotools need to be rerun and let the maintainer choose (you can suggest
+you would file a complete diff if the maintainer prefers).
 
 Last but not least, try to be courteous.
diff --git a/hurd/running/debian/porting.mdwn b/hurd/running/debian/porting.mdwn
index 16f39427..7ca91d37 100644
--- a/hurd/running/debian/porting.mdwn
+++ b/hurd/running/debian/porting.mdwn
@@ -1,4 +1,4 @@
-[[meta copyright="Copyright © 2008 Free Software Foundation, Inc."]]
+[[meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]]
 
 [[meta license="""[[toggle id="license" text="GFDL 1.2+"]][[toggleable
 id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -10,11 +10,22 @@ is included in the section entitled
 
 [[meta title="Debian packages that need porting"]]
 
-A large amount of Debian source packages can (by now) simple be built for
-Debian GNU/Hurd systems.
+Approximately half of the Debian archive has been compiled successfully on the
+Hurd, however, many programs fail to build for various reasons.
 
-Here are listed some of those (the important ones, as they're, e.g., blocking
-other packages from being built) that need someone to work on them.
+A [list of build failures including error
+messages](http://unstable.buildd.net/buildd/hurd-i386_Failed.html) can be
+found, as well as a [preliminary
+analysis](http://lists.debian.org/debian-hurd/2007/07/msg00000.html) of them.
+
+It might be a good idea to record your intention to port something either in
+the list below or in the [Alioth task
+tracker](http://alioth.debian.org/pm/task.php?group_project_id=34&group_id=30628&func=browse)
+so other people do not do duplicated work.
+
+Aside from the Alioth task tracker, here is a list of some packages (the
+important ones, as they're, e.g., blocking other packages from being built)
+that need someone to work on them.
 
 When you have a patch to submit, please adhere to the [[patch_submission]]
 guidelines.
diff --git a/hurd/running/debian/porting/gcc.mdwn b/hurd/running/debian/porting/gcc.mdwn
new file mode 100644
index 00000000..12982253
--- /dev/null
+++ b/hurd/running/debian/porting/gcc.mdwn
@@ -0,0 +1,50 @@
+[[meta copyright="Copyright © 2008 Free Software Foundation, Inc."]]
+
+[[meta license="""[[toggle id="license" text="GFDL 1.2+"]][[toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
+is included in the section entitled
+[[GNU_Free_Documentation_License|/fdl]]."]]"""]]
+
+For GCC trunk:
+
+Debian package has patches (for 4.3).  Some have been forwarded upstream.  (And
+have been ignored.)  [[Thomas_Schwinge|tschwinge]] is working on getting them
+integrated.
+
+  * [\[meta-bug\] bootstrap bugs for
+    \*-gnu\*](http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21824)
+
+      * [\[4.2/4.3/4.4 Regression\] GNU Hurd bootstrap error: 'OPTION\_GLIBC'
+        undeclared](http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28102)
+
+          * [Tool chain configuration: GNU/\* sharing stuff with
+            GNU/Linux](http://gcc.gnu.org/ml/gcc/2007-11/msg00289.html)
+
+          * [\[PATCH\] GNU/Hurd target
+            configuration](http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00344.html)
+
+  * [build system: gcc\_cv\_libc\_provides\_ssp and
+    NATIVE\_SYSTEM\_HEADER\_DIR](http://gcc.gnu.org/ml/gcc/2008-10/msg00130.html)
+
+      * [-fstack-protector shouldn't use TLS in freestanding
+        mode](http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29838)
+
+  * [Port libgcc's configury for
+    \*-\*-gnu\*](http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00315.html)
+
+
+Additionally:
+
+  * `libgcc/configure.ac` [might
+    need](http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00315.html) to be
+    aligned for us to the `*linux*` cases.  As well as at the end of
+    `libgcc/config.host`.  Check.
+
+        checking whether decimal floating point is supported... no
+        checking whether fixed-point is supported... no
+
+  * Also in other places: configure fragments that have `*linux*` cases
+    might/should often contain those for us (and GNU/k*BSD) as well.