From: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
To: "parisc-linux@thepuffingroup.com" <parisc-linux@thepuffingroup.com>
Subject: [parisc-linux] GCC compilation
Date: Mon, 08 Jan 2001 09:25:06 +0100 [thread overview]
Message-ID: <3A597962.77E53530@admin.france.hp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2360 bytes --]
Hi
I've retry to compil the GCC. It worked few weeks ago, but now it fails
when I try to compil the full GCC. This the output of my recompil script
(error output):
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:368: ISO C++ forbids
declaration of `pthread_mutex_t' with no type
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:368: parse error before ';'
token
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:580: syntax error before '<'
token
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:580: `__threads' was not
declared in this scope
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:580: `__inst' was not
declared in this scope
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:580: template argument 1 is
invalid
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:580: template argument 2 is
invalid
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:581: ISO C++ forbids
declaration of `_S_node_allocator_lock' with no type
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:581: `PTHREAD_MUTEX_INITIALIZER'
was not declared in this scope
In file included from /opt/linux_hppa/src/gcc/libstdc++/stdexcepti.cc:15:
/opt/linux_hppa/src/gcc/libstdc++/stdexcept:440: instantiated from here
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:393: `pthread_mutex_lock'
undeclared (first use this function)
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:393: (Each undeclared
identifier is reported only once for each function it appears in.)
In file included from /opt/linux_hppa/src/gcc/libstdc++/stdexcepti.cc:15:
/opt/linux_hppa/src/gcc/libstdc++/stdexcept:440: instantiated from here
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:394: `pthread_mutex_unlock'
undeclared (first use this function)
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h: In destructor
`logic_error::~logic_error ()':
/opt/linux_hppa/src/gcc/libstdc++/stl/stl_alloc.h:15: Internal error:
Segmentation fault.
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[1]: *** [stdexcepti.o] Error 1
make: *** [all-target-libstdc++] Error 2
Everything compil right, only the full GCC compil fail ? Do you have any idea ?
Must I redownload all bits ?
Thanks.
--
Vidal Bruno, (770-4271)
SSD-HA Team, HP-UX & LINUX Support
bruno_vidal@admin.france.hp.com
[-- Attachment #2: Card for Bruno Vidal --]
[-- Type: text/x-vcard, Size: 386 bytes --]
begin:vcard
n:Bruno;VIDAL
tel;fax:01-69-82-60-14
tel;work:01-69-29-42-71
x-mozilla-html:TRUE
url:www.france.hp.com
org:Solution Center
version:2.1
email;internet:bruno_vidal@hp.com
title:Expert Logiciel Environnement Haute Disponibilité
adr;quoted-printable:;;HP France=0D=0A;Z.A de Courtaboeuf;1 Av. du Canada;91947 Les Ulis cedex;France
x-mozilla-cpt:;26208
fn:VIDAL Bruno
end:vcard
next reply other threads:[~2001-01-08 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 8:25 Bruno Vidal [this message]
2001-01-08 8:28 ` [parisc-linux] GCC compilation Bruno Vidal
2001-01-08 10:17 ` Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A597962.77E53530@admin.france.hp.com \
--to=bruno_vidal@hpfrcu03.france.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox