public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Tobias Odensten" <mbox@bredband.net>
To: <gcc-help@gcc.gnu.org>
Subject: GCC-3.4.2 on Solaris9 install problem - No C++ headers
Date: Thu, 04 Nov 2004 23:01:00 -0000	[thread overview]
Message-ID: <000d01c4c2c2$2fcb8ed0$3400a8c0@bennyxp0qehfeg> (raw)

Hi!
Im experiencing problems when trying to install gcc-3.4.2 on Solaris 9. 
Apparently the c++ headers wont install properly. Im trying to build a 
compiler that supports c++ and ada. Please see below.

My system is a Sun Ultra30 with 128M mem and Solaris 9.

I download and install (from www.blastwave.org) the packages:
    common-1.3.3-SunOS5.8-sparc-CSW.pkg,
    gcc3rt-3.3.3,REV=2004.04.23-SunOS5.8-sparc-CSW.pkg and
    gcc3-3.3.3,REV=2004.03.22-SunOS5.8-sparc-CSW.pkg.
These packages install a complete gcc-3.3.3 with ada support.

Then I install: gnu-coreutils, gnu-tar, gnu-make, gnu-bison, gnu-flex and 
gnu-m4.

I download gcc-3.4.2.tar.bz2 from gcc.gnu.org and after unpacking, the 
source-files goes into /home/tobod/gcc-3.4.2 and the builddir 
/home/tobod/gcc-3.4.2-build is created.

In order to simplify things and save me some typing, I write a little 
install script (build_gcc-3.4.2-tmp):
--- start ---
umask 002
cd /home/tobod/gcc-3.4.2-build
# Build a gcc with only c++ and ada support, in /var/tmp/gcc:
env CFLAGS=-O2 CXXFLAGS=-O2 OPTIMIZE=-O2 STAGE1_CFLAGS=-O2 BOOT_CFLAGS=-O2 
LDFLAGS=-s 
/home/tobod/gcc-3.4.2/configure --prefix=/var/tmp/gcc --disable-shared --enable-languages=c,c++,ada 
 --with-pic
# Bootstrap the gcc.
gmake CFLAGS=-O2 CXXFLAGS=-O2 OPTIMIZE=-O2 STAGE1_CFLAGS=-O2 BOOT_CFLAGS=-O2 
LDFLAGS=-s bootstrap
# Build the gnatlib and tools:
cd /home/tobod/gcc-3.4.2-build/gcc
gmake CFLAGS=-O2 CXXFLAGS=-O2 OPTIMIZE=-O2 STAGE1_CFLAGS=-O2 BOOT_CFLAGS=-O2 
LDFLAGS=-s gnatlib_and_tools
# Install the gcc:
cd /home/tobod/gcc-3.4.2-build/gcc
gmake CFLAGS=-O2 CXXFLAGS=-O2 OPTIMIZE=-O2 STAGE1_CFLAGS=-O2 BOOT_CFLAGS=-O2 
LDFLAGS=-s install
--- end ---

To set some env variables I also write a script (set_env_tmp) containing env 
variable declarations:
--- start --
setenv PATH 
/opt/csw/gcc3/bin:/var/tmp/coreutils/bin:/var/tmp/gbin:/bin:/usr/bin:/usr/ccs/bin:/usr/sbin:/usr/local/bin:.
setenv MAKE gmake
setenv CC gcc
--- end ---

Then I do "source set_env_tmp and "sh build_gcc-3.4.2-tmp".

When the install script terminates, all applications in /var/tmp/gcc/bin 
seem to be OK (they are there!) BUT /var/tmp/gcc/include is completely 
empty! Some posts mention that the env variable CONFIG_SHELL should be set 
to /bin/ksh for the configure stage to work better, but all this seems to do 
is that some of the gnat-applications are missing after "install" has 
completed. Why oh why?? :(. Furthermore I tried to run the script with 
/bin/xpg4/sh instead of /bin/sh but it didnt do any good.

Questions: What target in /home/tobod/gcc-3.4.2-build/gcc/Makefile is 
responsible for the installation of the c++ headers? What did I do wrong!?

If someone out there could shed some light on this very extremely irritating 
mystery I would be very grateful.

/Tobias O 

                 reply	other threads:[~2004-11-04 23:01 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='000d01c4c2c2$2fcb8ed0$3400a8c0@bennyxp0qehfeg' \
    --to=mbox@bredband.net \
    --cc=gcc-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).