public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Arnold Vogelsang" <vogelsang@interactive-instruments.de>
To: <gcc@gcc.gnu.org>
Subject: Successful build of gcc-3.3.3 on alpha-dec-osf4.0f
Date: Thu, 18 Mar 2004 13:11:00 -0000	[thread overview]
Message-ID: <2BD59DF8C144A241813567D977492C31041B2A@andromeda.interactive-instruments.de> (raw)

Regards,

Arnold

Successful bootstrap build of gcc-3.3.3. Some tweaks were necessary.

Output from config.guess:

alpha-dec-osf4.0f

Output from gcc -v:

Reading specs from
/usr/user2/temp/gnu/gcc-3.3.3/bin/../lib/gcc-lib/alpha-dec-osf4.0f/3.3.3
/specs
Configured with: /temp/gcc-3.3.3/configure --prefix=/usr/local/gcc-3.3.3
--enable-version-specific-runtime-libs
--enable-threads=posix --enable-shared
--enable-languages=c,c++,f77,objc,java,ada --enable-libgcj
--with-gc=simple --enable-nls --enable-interpreter
--with-libiconv=/usr/local/libiconv-1.8
Thread model: posix
gcc version 3.3.3

Bootstrap build was started using gcc (version 2.95.3) and GNU make
(version 3.79.1)

Two files were modified in order to compile the java stuff without
errors (same as with gcc-3.3.2):

$srcdir/libjava/include/posix.h
   after line 65 inserted a line containing the declaration of usleep
(copied from unistd.h):
   extern void usleep __((unsigned int));

$srcdir/libjava/include/posix-threads.h:
   changed in line 251: #include <asm/pal.h> to #include <machine/pal.h>
   there is no asm directory present; there is an asm.h file instead
that inlcudes machine/pal.h

The following file took a very long time to compile during bootstrap
(same as with gcc-3.3.2,
about 2 hours cpu time):

$srcdir/libjava/verify.cc

--
Arnold Vogelsang  <vogelsang@interactive-instruments.de>

Die wiedergegebenen Meinungen vertreten nicht die Position meines
Arbeitgebers.

>> audiatur et altera pars <<

                 reply	other threads:[~2004-03-18 12:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2BD59DF8C144A241813567D977492C31041B2A@andromeda.interactive-instruments.de \
    --to=vogelsang@interactive-instruments.de \
    --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).