public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: markcia@nortelnetworks.com To: gcc-gnats@gcc.gnu.org Subject: bootstrap/5884: RUSAGE/PRUSAGE Compile Error with gcc-3.0.4 source Date: Fri, 08 Mar 2002 08:56:00 -0000 [thread overview] Message-ID: <20020308165133.19055.qmail@sources.redhat.com> (raw) >Number: 5884 >Category: bootstrap >Synopsis: RUSAGE/PRUSAGE Compile Error with gcc-3.0.4 source >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Mar 08 08:56:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Mark Cianfaglione >Release: upgrade from egcs-2.91.66 --> gcc-3.0.4 >Organization: >Environment: RH6.1 with kernel upgraded to 2.4.17 make at 3.79.1 stock libs of RH 6.1 >Description: Compilation of the latest GCC code (3.0.4) , upgrade from egcs-2.91.66, results in an several error messages `prus' has an incomplete type `RUSAGE_CHILDREN' undeclared Then compilation breaks down... I'm attaching the reported error >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="gcc_compile_error.txt" Content-Disposition: inline; filename="gcc_compile_error.txt" gcc -DIN_GCC -g -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I../../gcc-3.0.4/gcc -I../../gcc-3.0.4/gcc/. -I../../gcc-3.0.4/gcc/config -I../../gcc-3.0.4/gcc/../include \ -DSTANDARD_STARTFILE_PREFIX=\"../../../\" -DSTANDARD_EXEC_PREFIX=\"/usr/local/lib/gcc-lib/\" -DDEFAULT_TARGET_VERSION=\"3.0.4\" -DDEFAULT_TARGET_MACHINE=\"i686-pc-linux-gnu\" -DSTANDARD_BINDIR_PREFIX=\"/usr/local/bin/\" -DTOOLDIR_BASE_PREFIX=\"../../../../\" `test "X${SHLIB_LINK}" = "X" || test "yes" != "yes" || echo "-DENABLE_SHARED_LIBGCC"` `test "X${SHLIB_MULTILIB}" = "X" || echo "-DNO_SHARED_LIBGCC_MULTILIB"` \ -c ../../gcc-3.0.4/gcc/gcc.c) ../../gcc-3.0.4/gcc/gcc.c: In function `execute': ../../gcc-3.0.4/gcc/gcc.c:2720: `prus' has an incomplete type ../../gcc-3.0.4/gcc/gcc.c:2721: `RUSAGE_CHILDREN' undeclared (first use in this function) ../../gcc-3.0.4/gcc/gcc.c:2721: (Each undeclared identifier is reported only once ../../gcc-3.0.4/gcc/gcc.c:2721: for each function it appears in.) ../../gcc-3.0.4/gcc/gcc.c:2722: invalid use of undefined type `struct rusage' ../../gcc-3.0.4/gcc/gcc.c:2722: invalid use of undefined type `struct rusage' ../../gcc-3.0.4/gcc/gcc.c:2723: invalid use of undefined type `struct rusage' ../../gcc-3.0.4/gcc/gcc.c:2723: invalid use of undefined type `struct rusage' ../../gcc-3.0.4/gcc/gcc.c:2726: invalid use of undefined type `struct rusage' ../../gcc-3.0.4/gcc/gcc.c:2726: invalid use of undefined type `struct rusage' ../../gcc-3.0.4/gcc/gcc.c:2727: invalid use of undefined type `struct rusage' ../../gcc-3.0.4/gcc/gcc.c:2727: invalid use of undefined type `struct rusage' ../../gcc-3.0.4/gcc/gcc.c: At top level: ../../gcc-3.0.4/gcc/gcc.c:220: storage size of `rus' isn't known ../../gcc-3.0.4/gcc/gcc.c:220: storage size of `prus' isn't known make[2]: *** [gcc.o] Error 1 make[2]: Leaving directory `/gcctemp/gcc' make[1]: *** [stage1_build] Error 2 make[1]: Leaving directory `/gcctemp/gcc' make: *** [bootstrap] Error 2 [root@labrat /gcctemp]#
next reply other threads:[~2002-03-08 16:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-08 8:56 markcia [this message] 2002-03-15 20:29 rodrigc
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=20020308165133.19055.qmail@sources.redhat.com \ --to=markcia@nortelnetworks.com \ --cc=gcc-gnats@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).