public inbox for
help / color / mirror / Atom feed
From: Alexander Klimov <>
Subject: Re: bootstrap/10057: symbol is non-aligned
Date: Tue, 20 May 2003 13:26:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR bootstrap/10057; it has been noted by GNATS.

From: Alexander Klimov <>
To: Eric Botcazou <>
Cc: Dara Hazeghi <>, <>,
Subject: Re: bootstrap/10057: symbol is non-aligned
Date: Tue, 20 May 2003 16:18:53 +0300 (IDT)

 On Tue, 20 May 2003, Eric Botcazou wrote:
 > Yep, that's weird. For the record, I successfully bootstrapped on
 I still have the same error with 3.4 20030520
 > SunOS beeba 5.6 Generic_105181-31 sun4u sparc SUNW,Ultra-2
 SunOS iridium 5.6 Generic_105181-32 sun4u sparc SUNW,Ultra-5_10
 > cc: Sun WorkShop 6 update 2 C 5.3 Patch 111679-08 2002/05/09
 gcc 2.95.2
 > as: WorkShop Compilers 4.X dev 18 Sep 1996
 GNU assembler
 > ld: Software Generation Utilities - Solaris Link Editors: 5.6-1.274
 GNU ld version
 > with
 > gmake 'LIBCXXFLAGS=-g -O2 -fno-implicit-templates' bootstrap
 ../gcc/configure --prefix=/usr/local/gcc34 --with-cpu=ultrasparc
 --enable-languages=c,c++ && make CFLAGS=-O2 'LIBCFLAGS=-g -O2'
 'LIBCXXFLAGS=-g -O2 -fno-implicit-templates' bootstrap
 > results
 > beeba% gcc/xgcc -v
 > Using built-in specs.
 > Configured with: src/configure --prefix=/opt/TWWfsw/gcc34
 > --with-local-prefix=/opt/TWWfsw/gcc34 --with-cpu=ultrasparc
 > --enable-languages=c,c++ --enable-checking=misc,tree,rtlflag --disable-nls
 > Thread model: posix
 > gcc version 3.4 20030407 (experimental)
 Any ideas what is wrong with my setup?

             reply	other threads:[~2003-05-20 13:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 13:26 Alexander Klimov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-20 13:36 Eric Botcazou
2003-05-20 12:46 Eric Botcazou
2003-05-20  7:56 Dara Hazeghi
2003-05-19 12:56 Alexander Klimov
2003-05-17  1:16 Dara Hazeghi
2003-03-13  9:26 ask

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).