public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Michael J. McGillick" <mike@dunamis.ne.mediaone.net>
To: <help-gcc@gnu.org>
Subject: Building GCC
Date: Thu, 14 Sep 2000 05:43:00 -0000	[thread overview]
Message-ID: <000101c01e4a$053b9d20$c473f6c0@mercury> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4068 bytes --]

Good Morning:


I did a fresh install of HP-UX 11.00 on a PA-RISC machine - Model
9000/712/80.  I also applied the June 2000 extensions CD to make sure it has
all of the latest updates.  IÂ’m trying to get GCC built on this machine.
Here are the steps I followed:

·	I downloaded gcc-2.95.2.tar.gz from the GNU site.
·	I downloaded binutils-2.10.tar.gz from the GNU site.
·	I extracted both files into their respective directories.
·	I then copied from the binutils-2.10 directory the following directories
and placed them in the gcc-2.95.2 directory:
o	bfd
o	binutils
o	gas
o	ld
o	intl
o	opcodes

According to the directions in the GCC documents, by including these
directories, these will get built along with the compiler.  Again, this is a
clean system with absolutely no utilities on it other than what is shipped
out by HP.

I created a separate build folder as the instructions suggest, and I cd into
it.  I then type the following command:

   ../gcc-2.95.2/configure

The configure scripts chugs away happily for a few minutes.  It appears that
itÂ’s going through checking to see if my system has various things.  The
script starts off like this, and IÂ’m not sure if this is important or not:

Configuring for a hppa1.1-hp-hpux11.00 host.
*** This configuration is not supported in the following subdirectories:
     ld
    (Any other directories should still work fine.)
Created "Makefile" in /downloads/build-directory using "mh-frag"
(Bundled) cc: warning 480: The -g option is available only with the C/ANSI C
product; ignored.
Configuring intl...
creating cache ../config.cache
checking for a BSD compatible install...
../../gcc-2.95.2/intl/../install-sh -c
checking how to run the C preprocessor... cc -E
checking whether make sets ${MAKE}... yes
checking for gcc... cc
checking whether the C compiler (cc -g ) works... yes
checking whether the C compiler (cc -g ) is a cross-compiler... no
checking whether we are using GNU C... no
checking for ranlib... ranlib
checking for POSIXized ISC... no
checking for ANSI C header files... yes
checking for working const... no
checking for inline... no
checking for off_t... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for unistd.h... yes
checking for getpagesize... yes
checking for working mmap... no

The script continues to chug along, with only 1 warning showing up similar
to the one about the -g option not being available until it gets to this
point:

checking if the linker (/bin/ld) is GNU ld... no
checking whether the linker (/bin/ld) supports shared libraries... yes
checking command to parse /bin/nm -p output... yes
checking how to hardcode library paths into programs... relink
checking for /bin/ld option to reload object files... -r
checking dynamic linker characteristics... hpux11.00 dld.sl
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for objdir... .libs
creating libtool
loading cache ../config.cache
checking for gcc... (cached) cc
checking whether the C compiler (cc -g ) works... yes
checking whether the C compiler (cc -g ) is a cross-compiler... no
checking whether we are using GNU C... (cached) no
checking whether cc accepts -g... (cached) no
checking for bison... no
checking for byacc... no
checking how to run the C preprocessor... (cached) cc -E
checking for flex... no
checking for lex... no
../../gcc-2.95.2/binutils/configure[1935]: flex:  not found.
checking for flex... lex
checking for yywrap in -ll... yes
checking lex output file root... ../../gcc-2.95.2/binutils/configure[2023]:
lex:  not found.
configure: error: cannot find output from lex; giving up
Configure in /downloads/build-directory/binutils failed, exiting.

Here, the script just stops.

Any ideas what IÂ’m doing wrong here?  IÂ’m probably misunderstanding a lot of
what needs to be done.  Is there something that has to be installed on the
machine ahead of time, and canÂ’t be built initially?

- Mike

             reply	other threads:[~2000-09-14  5:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-14  5:43 Michael J. McGillick [this message]
2000-09-14 11:22 ` Alexandre Oliva
  -- strict thread matches above, loose matches on Subject: below --
2007-10-19  6:52 building gcc Myhuong Nguyen
2007-10-19 10:08 ` Kai Ruottu
2006-06-02 19:40 Building GCC Flop Bucket
2005-06-13  8:13 Frank Schafer
2005-06-13  9:02 ` Nathan Sidwell
2004-02-05  3:30 Help needed in compiling SSE2 asm code ganesh.yadav
2004-02-05  7:11 ` building gcc Dave Murphy
2001-10-10  0:20 Building gcc Frank Schafer
2001-10-10 19:24 ` Curtis R Anderson
2001-10-10 21:07   ` Frank Schafer
2001-09-26  8:50 building gcc Govind Vinjamuri
2001-09-28 17:49 ` Alexandre Oliva
1999-10-22 23:00 Building GCC Immanuel Andrew
1999-10-22 23:21 ` Tim Prince
1999-10-31 13:57   ` Tim Prince
1999-10-31 13:57 ` Immanuel Andrew

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='000101c01e4a$053b9d20$c473f6c0@mercury' \
    --to=mike@dunamis.ne.mediaone.net \
    --cc=help-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).