public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Robert McNulty Junior" <bmj2001@bellsouth.net>
To: <gcc@gcc.gnu.org>
Subject: GCC 3.3-Signal 11
Date: Wed, 05 Feb 2003 00:39:00 -0000	[thread overview]
Message-ID: <GGEKKFKDCKKAHNCJOFCNGEDMCAAA.bmj2001@bellsouth.net> (raw)


This is where the fault is at.


____________________________________________________________________________
________________
for f in $gf; do \
echo "\"$f\", "; done >> tmp-gtyp.h
echo " NULL};" >> tmp-gtyp.h
echo "static const char *lang_dir_names[] = { \"c\", " >> tmp-gtyp.h
gf="cp f java objc"; \
for l in $gf; do \
echo "\"$l\", "; done >> tmp-gtyp.h
echo "NULL};" >> tmp-gtyp.h
/bin/sh ../../gcc/gcc/move-if-change tmp-gtyp.h gtyp-gen.h
gcc -c   -g  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissi
ng-p
rototypes -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H -DGENERAT
OR_F
ILE   -DCYGWIN_CROSS_DIR=\"/usr/local/i686-pc-cygwin\" -I. -I. -I../../gcc/g
cc -
I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include \
  ../../gcc/gcc/gengtype.c -o gengtype.o
gcc -c   -g  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissi
ng-p
rototypes -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H -DGENERAT
OR_F
ILE   -DCYGWIN_CROSS_DIR=\"/usr/local/i686-pc-cygwin\" -I. -I. -I../../gcc/g
cc -
I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include \
  ../../gcc/gcc/gengtype-lex.c -o gengtype-lex.o
gcc -c   -g  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissi
ng-p
rototypes -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H -DGENERAT
OR_F
ILE   -DCYGWIN_CROSS_DIR=\"/usr/local/i686-pc-cygwin\" -I. -I. -I../../gcc/g
cc -
I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include \
  ../../gcc/gcc/gengtype-yacc.c -o gengtype-yacc.o
gcc   -g  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
prot
otypes -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H -DGENERATOR_
FILE
  -o gengtype.exe \
 gengtype.o gengtype-lex.o gengtype-yacc.o ../libiberty/libiberty.a
./gengtype
Signal 11
make[2]: *** [s-gtype] Error 139
make[2]: Leaving directory `/home/Robert/gcc-3.3/o/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/home/Robert/gcc-3.3/o/gcc'
make: *** [bootstrap] Error 2

Robert@bobby ~/gcc-3.3/o
$


             reply	other threads:[~2003-02-05  0:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05  0:39 Robert McNulty Junior [this message]
2003-02-07  4:19 ` Kelley Cook
2003-02-07  5:15   ` Kelley Cook
2003-02-07  5:58     ` Robert McNulty Junior

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=GGEKKFKDCKKAHNCJOFCNGEDMCAAA.bmj2001@bellsouth.net \
    --to=bmj2001@bellsouth.net \
    --cc=gcc@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).