GNU bug report logs - #28284
GCC 4.7.4 fails to build since April 2017

Previous Next

Package: guix;

Reported by: Mark H Weaver <mhw <at> netris.org>

Date: Tue, 29 Aug 2017 21:28:02 UTC

Severity: normal

Done: Jan Nieuwenhuizen <janneke <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 28284 in the body.
You can then email your comments to 28284 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#28284; Package guix. (Tue, 29 Aug 2017 21:28:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mark H Weaver <mhw <at> netris.org>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 29 Aug 2017 21:28:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: bug-guix <at> gnu.org
Subject: GCC 4.7.4 fails to build since April 2017
Date: Tue, 29 Aug 2017 17:26:59 -0400
GCC 4.7.4 fails to build since April 2017:

  https://hydra.gnu.org/job/gnu/master/gcc-4.7.4.x86_64-linux
  https://hydra.gnu.org/job/gnu/master/gcc-4.7.4.i686-linux

      Mark




Information forwarded to bug-guix <at> gnu.org:
bug#28284; Package guix. (Mon, 06 Nov 2017 22:00:04 GMT) Full text and rfc822 format available.

Message #8 received at 28284 <at> debbugs.gnu.org (full text, mbox):

From: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: Mark H Weaver <mhw <at> netris.org>
Cc: 28284 <at> debbugs.gnu.org
Subject: Re: bug#28284: GCC 4.7.4 fails to build since April 2017
Date: Mon, 06 Nov 2017 22:58:28 +0100
[Message part 1 (text/plain, inline)]
Mark H Weaver writes:

> GCC 4.7.4 fails to build since April 2017:
>
>   https://hydra.gnu.org/job/gnu/master/gcc-4.7.4.x86_64-linux
>   https://hydra.gnu.org/job/gnu/master/gcc-4.7.4.i686-linux

The attached patch should fix this.  I tested it on an inherited package
like this below, while attempting to create diverse double compilation

(define-public repro-gcc-4.7
  (package
    (inherit gcc-4.7-$ORIGIN)
    (source
     (origin
       (inherit (package-source gcc-4.7-$ORIGIN))
       (patches (append ((compose origin-patches package-source) gcc-4.7)
                        (search-patches "gcc-5-reproducibility-drop-profile.patch"
                                        "gcc-4-cfns-fix-mismatch-in-gnu_inline-attributes.patch"
                                        "gcc-4-build-path-prefix-map.patch")))))
    (name "repro-gcc")
    (version "4.7.4")
    (arguments
     (substitute-keyword-arguments (package-arguments gcc-4.7-$ORIGIN)
       ((#:phases original-phases)
        `(modify-phases ,original-phases
           (add-before 'configure 'build-prefix-path
             (lambda* (#:key inputs #:allow-other-keys)
               (setenv "BUILD_PATH_PREFIX_MAP"
                       (string-append "gcc" "-" ,version "=" (getcwd)))
               (format (current-error-port)
                       "BUILD_PATH_PREFIX_MAP=~s\n"
                       (getenv "BUILD_PATH_PREFIX_MAP"))))))))))

Greetings,
janneke

[0001-gnu-gcc-4.7-Resurrect-building-with-gcc-5.4.0.patch (text/x-patch, inline)]
From b2fb0adc3e0de7194493a0c5f1f9bbdbcd0a4087 Mon Sep 17 00:00:00 2001
From: Jan Nieuwenhuizen <janneke <at> gnu.org>
Date: Mon, 6 Nov 2017 22:50:05 +0100
Subject: [PATCH] gnu: gcc-4.7: Resurrect building with gcc-5.4.0.

* gnu/packages/patches/gcc-4-cfns-fix-mismatch-in-gnu_inline-attributes.patch:
New file.
* gnu/local.mk (dist_patch_DATA): Add it.
* gnu/packages/gcc.scm (gcc-4.7): Use it.
---
 gnu/local.mk                                       |  1 +
 gnu/packages/gcc.scm                               |  3 +
 ...fns-fix-mismatch-in-gnu_inline-attributes.patch | 65 ++++++++++++++++++++++
 3 files changed, 69 insertions(+)
 create mode 100644 gnu/packages/patches/gcc-4-cfns-fix-mismatch-in-gnu_inline-attributes.patch

diff --git a/gnu/local.mk b/gnu/local.mk
index 5dfcf497b..76aef903a 100644
--- a/gnu/local.mk
+++ b/gnu/local.mk
@@ -637,6 +637,7 @@ dist_patch_DATA =						\
   %D%/packages/patches/gcc-cross-environment-variables.patch	\
   %D%/packages/patches/gcc-libvtv-runpath.patch			\
   %D%/packages/patches/gcc-strmov-store-file-names.patch	\
+  %D%/packages/patches/gcc-4-cfns-fix-mismatch-in-gnu_inline-attributes.patch \
   %D%/packages/patches/gcc-4.6-gnu-inline.patch			\
   %D%/packages/patches/gcc-4.9.3-mingw-gthr-default.patch	\
   %D%/packages/patches/gcc-5.0-libvtv-runpath.patch		\
diff --git a/gnu/packages/gcc.scm b/gnu/packages/gcc.scm
index 7870d4513..2991cbd0b 100644
--- a/gnu/packages/gcc.scm
+++ b/gnu/packages/gcc.scm
@@ -136,6 +136,9 @@ where the OS part is overloaded to denote a specific ABI---into GCC
                (method url-fetch)
                (uri (string-append "mirror://gnu/gcc/gcc-"
                                    version "/gcc-" version ".tar.bz2"))
+               (patches
+                (search-patches
+                 "gcc-4-cfns-fix-mismatch-in-gnu_inline-attributes.patch"))
                (sha256
                 (base32
                  "10k2k71kxgay283ylbbhhs51cl55zn2q38vj5pk4k950qdnirrlj"))))
diff --git a/gnu/packages/patches/gcc-4-cfns-fix-mismatch-in-gnu_inline-attributes.patch b/gnu/packages/patches/gcc-4-cfns-fix-mismatch-in-gnu_inline-attributes.patch
new file mode 100644
index 000000000..861cd4857
--- /dev/null
+++ b/gnu/packages/patches/gcc-4-cfns-fix-mismatch-in-gnu_inline-attributes.patch
@@ -0,0 +1,65 @@
+Taken from  https://gcc.gnu.org/cgi-bin/get-raw-msg?listname=gcc-patches&date=2016-01&msgid=1451802493-17406-1-git-send-email-vapier%40gentoo.org
+
+Since the 3.0.3 release of gperf (made in May 2007), the generated func
+has had the gnu_inline attribute applied to it.  The gcc source however
+has not been updated to include that which has lead to a mismatch.
+
+In practice, this hasn't been an issue for two reasons:
+(1) Before gcc-5, the default standard was (gnu) C89, and gcc does not
+warn or throw an error in this mode.
+(2) Starting with gcc-4.8, the compiler driver used to build gcc was
+changed to C++, and g++ does not warn or throw an error in this mode.
+
+This error does show up though when using gcc-5 to build gcc-4.7 or
+older as then the default is (gnu) C11 and the C compiler driver is
+used.  That failure looks like:
+In file included from .../gcc-4.7.4/gcc/cp/except.c:990:0:
+cfns.gperf: At top level:
+cfns.gperf:101:1: error: 'gnu_inline' attribute present on 'libc_name_p'
+cfns.gperf:26:14: error: but not here
+
+Whether the compiler should always emit this error regardless of the
+active standard or compiler driver is debatable (I think it should be
+consistent -- either always do it or never do it).
+
+2015-08-06  Mike Frysinger  <vapier <at> gentoo.org>
+
+	* cfns.gperf [__GNUC__, __GNUC_STDC_INLINE__]: Apply the
+	__gnu_inline__ attribute.
+	* cfns.h: Regenerated.
+---
+ gcc/cp/cfns.gperf | 3 +++
+ gcc/cp/cfns.h     | 3 +++
+ 2 files changed, 6 insertions(+)
+
+diff --git a/gcc/cp/cfns.gperf b/gcc/cp/cfns.gperf
+index 68acd3d..953262f 100644
+--- a/gcc/cp/cfns.gperf
++++ b/gcc/cp/cfns.gperf
+@@ -22,6 +22,9 @@ __inline
+ static unsigned int hash (const char *, unsigned int);
+ #ifdef __GNUC__
+ __inline
++#ifdef __GNUC_STDC_INLINE__
++__attribute__ ((__gnu_inline__))
++#endif
+ #endif
+ const char * libc_name_p (const char *, unsigned int);
+ %}
+diff --git a/gcc/cp/cfns.h b/gcc/cp/cfns.h
+index 1c6665d..6d00c0e 100644
+--- a/gcc/cp/cfns.h
++++ b/gcc/cp/cfns.h
+@@ -53,6 +53,9 @@ __inline
+ static unsigned int hash (const char *, unsigned int);
+ #ifdef __GNUC__
+ __inline
++#ifdef __GNUC_STDC_INLINE__
++__attribute__ ((__gnu_inline__))
++#endif
+ #endif
+ const char * libc_name_p (const char *, unsigned int);
+ /* maximum key range = 391, duplicates = 0 */
+-- 
+2.6.2
+
-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

[Message part 3 (text/plain, inline)]
-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

Information forwarded to bug-guix <at> gnu.org:
bug#28284; Package guix. (Tue, 07 Nov 2017 10:26:02 GMT) Full text and rfc822 format available.

Message #11 received at 28284 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke <at> gnu.org>
Cc: Mark H Weaver <mhw <at> netris.org>, 28284 <at> debbugs.gnu.org
Subject: Re: bug#28284: GCC 4.7.4 fails to build since April 2017
Date: Tue, 07 Nov 2017 11:25:24 +0100
Hello!

Jan Nieuwenhuizen <janneke <at> gnu.org> skribis:

> From b2fb0adc3e0de7194493a0c5f1f9bbdbcd0a4087 Mon Sep 17 00:00:00 2001
> From: Jan Nieuwenhuizen <janneke <at> gnu.org>
> Date: Mon, 6 Nov 2017 22:50:05 +0100
> Subject: [PATCH] gnu: gcc-4.7: Resurrect building with gcc-5.4.0.
>
> * gnu/packages/patches/gcc-4-cfns-fix-mismatch-in-gnu_inline-attributes.patch:
> New file.

Could you use a shorter file name, so we don't hit tar’s limit on file
name length?

> * gnu/local.mk (dist_patch_DATA): Add it.
> * gnu/packages/gcc.scm (gcc-4.7): Use it.

I think this can actually go to master, though please double-check that
the world isn’t getting rebuilt.  :-)

Thank you!

Ludo’.




Information forwarded to bug-guix <at> gnu.org:
bug#28284; Package guix. (Tue, 07 Nov 2017 17:31:02 GMT) Full text and rfc822 format available.

Message #14 received at 28284 <at> debbugs.gnu.org (full text, mbox):

From: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: Mark H Weaver <mhw <at> netris.org>, 28284 <at> debbugs.gnu.org
Subject: Re: bug#28284: GCC 4.7.4 fails to build since April 2017
Date: Tue, 07 Nov 2017 18:29:51 +0100
[Message part 1 (text/plain, inline)]
Ludovic Courtès writes:

>> * gnu/packages/patches/gcc-4-cfns-fix-mismatch-in-gnu_inline-attributes.patch:
>> New file.
>
> Could you use a shorter file name, so we don't hit tar’s limit on file
> name length?

I chose: gcc-4-compile-with-gcc-5.patch.  New patch attached.

>> * gnu/local.mk (dist_patch_DATA): Add it.
>> * gnu/packages/gcc.scm (gcc-4.7): Use it.
>
> I think this can actually go to master, though please double-check that
> the world isn’t getting rebuilt.  :-)

Here is what I did

    18:25:50 janneke <at> dundal:~/src/guix-master [env]
    $ ./pre-inst-env guix refresh -l gcc <at> 4.7.4
    No dependents other than itself: gcc <at> 4.7.4
    18:25:55 janneke <at> dundal:~/src/guix-master [env]
    $ ./pre-inst-env guix build hello
    /gnu/store/lr8c1yswvrgckkaa6nzdi7q0d618bazs-hello-2.10
    18:26:01 janneke <at> dundal:~/src/guix-master [env]

so indeed, it looks fine; and it makes sense.  I was working on the
$ORIGIN stuff inside (a copy of) the gcc-4.7.4 builder -- that code is
of course (re)used by all other gcc packages.

Greetings,
janneke

[0001-gnu-gcc-4.7-Resurrect-building-with-gcc-5.4.0.patch (text/x-patch, inline)]
From 22d5353991784409e3a8e671611c5ccff3ff7b68 Mon Sep 17 00:00:00 2001
From: Jan Nieuwenhuizen <janneke <at> gnu.org>
Date: Mon, 6 Nov 2017 22:50:05 +0100
Subject: [PATCH] gnu: gcc-4.7: Resurrect building with gcc-5.4.0.

* gnu/packages/patches/gcc-4-compile-with-gcc-5.patch: New file.
* gnu/local.mk (dist_patch_DATA): Add it.
* gnu/packages/gcc.scm (gcc-4.7): Use it.
---
 gnu/local.mk                                       |  2 +
 gnu/packages/gcc.scm                               |  1 +
 .../patches/gcc-4-compile-with-gcc-5.patch         | 65 ++++++++++++++++++++++
 3 files changed, 68 insertions(+)
 create mode 100644 gnu/packages/patches/gcc-4-compile-with-gcc-5.patch

diff --git a/gnu/local.mk b/gnu/local.mk
index 630d8187f..c77c4d8ed 100644
--- a/gnu/local.mk
+++ b/gnu/local.mk
@@ -11,6 +11,7 @@
 # Copyright © 2016 Ben Woodcroft <donttrustben <at> gmail.com>
 # Copyright © 2016, 2017 Alex Vong <alexvong1995 <at> gmail.com>
 # Copyright © 2016, 2017 Efraim Flashner <efraim <at> flashner.co.il>
+# Copyright © 2016, 2017 Jan Nieuwenhuizen <janneke <at> gnu.org>
 # Copyright © 2017 Tobias Geerinckx-Rice <me <at> tobias.gr>
 # Copyright © 2017 Clément Lassieur <clement <at> lassieur.org>
 # Copyright © 2017 Mathieu Othacehe <m.othacehe <at> gmail.com>
@@ -637,6 +638,7 @@ dist_patch_DATA =						\
   %D%/packages/patches/gcc-cross-environment-variables.patch	\
   %D%/packages/patches/gcc-libvtv-runpath.patch			\
   %D%/packages/patches/gcc-strmov-store-file-names.patch	\
+  %D%/packages/patches/gcc-4-compile-with-gcc-5.patch		 \
   %D%/packages/patches/gcc-4.6-gnu-inline.patch			\
   %D%/packages/patches/gcc-4.9.3-mingw-gthr-default.patch	\
   %D%/packages/patches/gcc-5.0-libvtv-runpath.patch		\
diff --git a/gnu/packages/gcc.scm b/gnu/packages/gcc.scm
index 7870d4513..79e159f1a 100644
--- a/gnu/packages/gcc.scm
+++ b/gnu/packages/gcc.scm
@@ -136,6 +136,7 @@ where the OS part is overloaded to denote a specific ABI---into GCC
                (method url-fetch)
                (uri (string-append "mirror://gnu/gcc/gcc-"
                                    version "/gcc-" version ".tar.bz2"))
+               (patches (search-patches "gcc-4-compile-with-gcc-5.patch"))
                (sha256
                 (base32
                  "10k2k71kxgay283ylbbhhs51cl55zn2q38vj5pk4k950qdnirrlj"))))
diff --git a/gnu/packages/patches/gcc-4-compile-with-gcc-5.patch b/gnu/packages/patches/gcc-4-compile-with-gcc-5.patch
new file mode 100644
index 000000000..861cd4857
--- /dev/null
+++ b/gnu/packages/patches/gcc-4-compile-with-gcc-5.patch
@@ -0,0 +1,65 @@
+Taken from  https://gcc.gnu.org/cgi-bin/get-raw-msg?listname=gcc-patches&date=2016-01&msgid=1451802493-17406-1-git-send-email-vapier%40gentoo.org
+
+Since the 3.0.3 release of gperf (made in May 2007), the generated func
+has had the gnu_inline attribute applied to it.  The gcc source however
+has not been updated to include that which has lead to a mismatch.
+
+In practice, this hasn't been an issue for two reasons:
+(1) Before gcc-5, the default standard was (gnu) C89, and gcc does not
+warn or throw an error in this mode.
+(2) Starting with gcc-4.8, the compiler driver used to build gcc was
+changed to C++, and g++ does not warn or throw an error in this mode.
+
+This error does show up though when using gcc-5 to build gcc-4.7 or
+older as then the default is (gnu) C11 and the C compiler driver is
+used.  That failure looks like:
+In file included from .../gcc-4.7.4/gcc/cp/except.c:990:0:
+cfns.gperf: At top level:
+cfns.gperf:101:1: error: 'gnu_inline' attribute present on 'libc_name_p'
+cfns.gperf:26:14: error: but not here
+
+Whether the compiler should always emit this error regardless of the
+active standard or compiler driver is debatable (I think it should be
+consistent -- either always do it or never do it).
+
+2015-08-06  Mike Frysinger  <vapier <at> gentoo.org>
+
+	* cfns.gperf [__GNUC__, __GNUC_STDC_INLINE__]: Apply the
+	__gnu_inline__ attribute.
+	* cfns.h: Regenerated.
+---
+ gcc/cp/cfns.gperf | 3 +++
+ gcc/cp/cfns.h     | 3 +++
+ 2 files changed, 6 insertions(+)
+
+diff --git a/gcc/cp/cfns.gperf b/gcc/cp/cfns.gperf
+index 68acd3d..953262f 100644
+--- a/gcc/cp/cfns.gperf
++++ b/gcc/cp/cfns.gperf
+@@ -22,6 +22,9 @@ __inline
+ static unsigned int hash (const char *, unsigned int);
+ #ifdef __GNUC__
+ __inline
++#ifdef __GNUC_STDC_INLINE__
++__attribute__ ((__gnu_inline__))
++#endif
+ #endif
+ const char * libc_name_p (const char *, unsigned int);
+ %}
+diff --git a/gcc/cp/cfns.h b/gcc/cp/cfns.h
+index 1c6665d..6d00c0e 100644
+--- a/gcc/cp/cfns.h
++++ b/gcc/cp/cfns.h
+@@ -53,6 +53,9 @@ __inline
+ static unsigned int hash (const char *, unsigned int);
+ #ifdef __GNUC__
+ __inline
++#ifdef __GNUC_STDC_INLINE__
++__attribute__ ((__gnu_inline__))
++#endif
+ #endif
+ const char * libc_name_p (const char *, unsigned int);
+ /* maximum key range = 391, duplicates = 0 */
+-- 
+2.6.2
+
-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

[Message part 3 (text/plain, inline)]
-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

Information forwarded to bug-guix <at> gnu.org:
bug#28284; Package guix. (Tue, 07 Nov 2017 20:59:01 GMT) Full text and rfc822 format available.

Message #17 received at 28284 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke <at> gnu.org>
Cc: Mark H Weaver <mhw <at> netris.org>, 28284 <at> debbugs.gnu.org
Subject: Re: bug#28284: GCC 4.7.4 fails to build since April 2017
Date: Tue, 07 Nov 2017 21:58:45 +0100
Jan Nieuwenhuizen <janneke <at> gnu.org> skribis:

> Here is what I did
>
>     18:25:50 janneke <at> dundal:~/src/guix-master [env]
>     $ ./pre-inst-env guix refresh -l gcc <at> 4.7.4
>     No dependents other than itself: gcc <at> 4.7.4
>     18:25:55 janneke <at> dundal:~/src/guix-master [env]
>     $ ./pre-inst-env guix build hello
>     /gnu/store/lr8c1yswvrgckkaa6nzdi7q0d618bazs-hello-2.10
>     18:26:01 janneke <at> dundal:~/src/guix-master [env]
>
> so indeed, it looks fine; and it makes sense.

Sounds good.

> I was working on the $ORIGIN stuff inside (a copy of) the gcc-4.7.4
> builder -- that code is of course (re)used by all other gcc packages.

Though the $ORIGIN stuff is separate, right?  Will be nice to have.

> From 22d5353991784409e3a8e671611c5ccff3ff7b68 Mon Sep 17 00:00:00 2001
> From: Jan Nieuwenhuizen <janneke <at> gnu.org>
> Date: Mon, 6 Nov 2017 22:50:05 +0100
> Subject: [PATCH] gnu: gcc-4.7: Resurrect building with gcc-5.4.0.
>
> * gnu/packages/patches/gcc-4-compile-with-gcc-5.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Add it.
> * gnu/packages/gcc.scm (gcc-4.7): Use it.

Go for it!

Thank you,
Ludo’.




Reply sent to Jan Nieuwenhuizen <janneke <at> gnu.org>:
You have taken responsibility. (Tue, 07 Nov 2017 21:09:01 GMT) Full text and rfc822 format available.

Notification sent to Mark H Weaver <mhw <at> netris.org>:
bug acknowledged by developer. (Tue, 07 Nov 2017 21:09:02 GMT) Full text and rfc822 format available.

Message #22 received at 28284-done <at> debbugs.gnu.org (full text, mbox):

From: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: Mark H Weaver <mhw <at> netris.org>, 28284-done <at> debbugs.gnu.org
Subject: Re: bug#28284: GCC 4.7.4 fails to build since April 2017
Date: Tue, 07 Nov 2017 22:07:53 +0100
Ludovic Courtès writes:

>> I was working on the $ORIGIN stuff inside (a copy of) the gcc-4.7.4
>> builder -- that code is of course (re)used by all other gcc packages.
>
> Though the $ORIGIN stuff is separate, right?  Will be nice to have.

Sure, i figure this will take some time to get in if at all.  We'll have
to see what the pros and cons are.  Different story/thread.

>> From 22d5353991784409e3a8e671611c5ccff3ff7b68 Mon Sep 17 00:00:00 2001
>> From: Jan Nieuwenhuizen <janneke <at> gnu.org>
>> Date: Mon, 6 Nov 2017 22:50:05 +0100
>> Subject: [PATCH] gnu: gcc-4.7: Resurrect building with gcc-5.4.0.
>>
>> * gnu/packages/patches/gcc-4-compile-with-gcc-5.patch: New file.
>> * gnu/local.mk (dist_patch_DATA): Add it.
>> * gnu/packages/gcc.scm (gcc-4.7): Use it.
>
> Go for it!

Pushed to master as 625492ee1a5a8e515b97d4b76734584c1b420243

janneke

-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Wed, 06 Dec 2017 12:24:08 GMT) Full text and rfc822 format available.

This bug report was last modified 6 years and 114 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.