public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: joshudson@hotmail.com
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/6763: bootstrap failed due to missing header file
Date: Tue, 21 May 2002 20:56:00 -0000	[thread overview]
Message-ID: <20020522035330.7640.qmail@sources.redhat.com> (raw)


>Number:         6763
>Category:       bootstrap
>Synopsis:       bootstrap failed due to missing header file
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 21 20:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Joshua Hudson
>Release:        gcc-3.1
>Organization:
>Environment:
Zipslack 3.5
>Description:
Trying to build on zipslack 3.5 for another system
PWD=/root/gccb
../gcc-*/configure --host=i586-pc-linux-gnulibc1 --libdir=/root/lib
Configures w/o any errors or warnings

make bootstrap
finally dies with:

mkdir libgcc
if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
./xgcc -B./ -B/usr/local/i586-pc-linux-gnulibc1/bin/
     -isystem /usr/local/i586-pc-linux-gnulibc1/include
     -isystem /usr/local/i586-pc-linux-gnulibc1/sys-include -O2  -DIN_GCC
     -DUSE_GNULIBC_1 -W -Wall -Wwrite-strings -Wstrict-prototypes
     -Wmissing-prototypes -isystem ./include  -fPIC -g  -DIN_LIBGCC2
     -D__GCC_FLOAT_NOT_NEEDED  -I. -I.
     -I../../gcc-3.1/gcc -I../../gcc-3.1/gcc/. -I../../gcc-3.1/gcc/config
     -I../../gcc-3.1/gcc/../include  -DL_muldi3 -c ../../gcc-3.1/gcc/libgcc2.c
     -o libgcc/./_muldi3.o
In file included from tconfig.h:21,
     from ../../gcc-3.1/gcc/libgcc2.c:36:
     ../../gcc-3.1/gcc/config/i386/linux.h:225:26: sys/ucontext.h: No such file
     or directory
make[3]: *** [libgcc/./_muldi3.o] Error 1

The only prior events are warnings of comparing signed with unsigned.
The final destination for this build is a machine running muLinux
(i586 linux 2.0.36 libc.so.5.4.13)

/root/lib contains all libraries available on target platform.
>How-To-Repeat:
I don't know if something is wrong with GCC or my
build environment. I lack a better machine to test on.
Can't get enough disk space to build on target machine.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-22  3:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 20:56 joshudson [this message]
2002-10-24 16:53 hp

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=20020522035330.7640.qmail@sources.redhat.com \
    --to=joshudson@hotmail.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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).