From: Robert A Nesius <rnesius@ichips.intel.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Paul DeMello <paul@oax.com>, <gcc-help@gcc.gnu.org>
Subject: Re: building gcc/g++ 3.0 on aix: gen-num-limits failed to execute
Date: Tue, 10 Jul 2001 15:16:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0107101406060.28219-100000@plxw0032.pdx.intel.com> (raw)
In-Reply-To: <or4rslzbb7.fsf@guarana.lsd.ic.unicamp.br>
On 10 Jul 2001, Alexandre Oliva wrote:
> On Jul 9, 2001, "Paul DeMello" <paul@oax.com> wrote:
>
> > ./configure --enable-threads=pthreads
>
> > Cannot run a 64-bit program on a 32-bit machine.
>
> Add --disable-aix64 to the configure command line.
>
> But beware: C++ exception handling is quite broken on AIX in GCC 3.0,
> unfortunately. Hopefully, the problems are going to be fixed in time
> for GCC 3.0.1.
I broke down in a similar place. This is after the compiler has
bootstrapped. Line 178 in mknumeric_limits is the area where
that script tries to compile gen-num-limits but I wasn't able to root
cause it. I ran the compile that dumped core by hand and it worked
fine. Running 'gmake bootstrap' again got the build to continue
on its way (it is still building - takes over 14 hours for this
build to complete on this machine/os).
--host=rs6000-ibm-aix4.1.4.0
-Rob
============================
<...>
with_multisubdir=powerpc
running mkc++config
running mknumeric_limits
/fs29/comp.apps.3/00r1.builds/rnesius/gcc-3.0/aix4/gcc/xgcc -B/fs29/comp.apps.3/00r1.builds/rnesius/gcc-3.0/aix4/gcc/ -B/usr/intel/pkgs/gcc/3.0/rs6000-ibm-aix4.1.4.0/bin/ -B/usr/intel/pkgs/gcc/3.0/rs6000-ibm-aix4.1.4.0/lib/ -isystem /usr/intel/pkgs/gcc/3.0/rs6000-ibm-aix4.1.4.0/include -mcpu=powerpc -I. -I/fs29/comp.apps.3/00r1.builds/rnesius/gcc-3.0/aix4/rs6000-ibm-aix4.1.4.0/powerpc/libstdc++-v3/include -DHAVE_CONFIG_H -fno-exceptions -o /fs29/comp.apps.3/00r1.builds/rnesius/gcc-3.0/aix4/rs6000-ibm-aix4.1.4.0/powerpc/libstdc++-v3/src/gen-num-limits ../../../../gcc-3.0/libstdc++-v3/src/gen-num-limits.cc
../../../../gcc-3.0/libstdc++-v3/mknumeric_limits[178]: 39000 Illegal instruction(coredump)
gen-num-limits failed to execute, exiting.
mknumeric_limits failed to execute properly: exiting
gmake[1]: *** [configure-target-libstdc++-v3] Error 1
gmake[1]: Leaving directory `/auto_mnt/pdxfs29/fs29/comp.apps.3/00r1.builds/rnesius/gcc-3.0/aix4'
gmake: *** [bootstrap] Error 2
-Rob
--
#include <sig.h>
------------------------------------------------------------------
Robert Nesius rnesius@ichips.intel.com 503.712.2181
DPG Engineering Computing SW Applications Team
next prev parent reply other threads:[~2001-07-10 15:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 17:34 Paul DeMello
2001-07-09 20:56 ` Alexandre Oliva
2001-07-10 15:16 ` Robert A Nesius [this message]
2001-07-10 18:42 ` Alexandre Oliva
2001-07-10 16:08 ` Paul DeMello
2001-07-10 18:39 ` Alexandre Oliva
2001-07-11 7:59 ` Paul DeMello
2001-07-11 23:17 ` "internal compiler error" --gcc-2.95.3 Piotr Stachura
2001-07-27 0:59 ` Alexandre Oliva
2001-07-29 22:36 ` Piotr Stachura
2001-07-30 14:28 ` Alexandre Oliva
2001-07-27 1:05 ` building gcc/g++ 3.0 on aix: gen-num-limits failed to execute Alexandre Oliva
2001-07-27 7:43 ` Paul DeMello
2001-07-28 20:17 ` Alexandre Oliva
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=Pine.LNX.4.30.0107101406060.28219-100000@plxw0032.pdx.intel.com \
--to=rnesius@ichips.intel.com \
--cc=aoliva@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=paul@oax.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).