Thank you all for you replies and suggestions (see below).
I should mention that I am successful with building C++ if I use the following commands:
configure
make bootstrap LANGUAGES="c c++ objective-c"
make install LANGUAGES="c c++ objective-c"
However, if I do the compilation in the various stages, it will fail (i.e. configure, make CC=gcc LANGUAGES=c, make stage1, make stage2, etc.). For some reason, when using GCC to compile the source it just won't work. Anyhow, I do have GCC compiled.
Now, my problem is with building the LIBG++...<arg>... this just doesn't seem to be getting any better! I will post the errors I'm getting in a separate message. I would most appreciate it if someone may know something to help me with this troubling stumbling block!
Thanks again.
Ju
julienlim@rocketmail.com
----------------------------------------------------------------------
Gavin Brennan [btigb@ui.uis.doleta.gov]:
Please forgive me if I'm still missing the point, but why not
pull down the compiled gcc, use it to compile your own gcc
where and how you like it, then use your own version of gcc
to compile perl, gb and so on?
BTW, by a system "which doesn't have the complete O/S" do you
mean one that does not have a working cc? (So that Sun can sell
the unbundled compiler separately.) Or are there other pieces
missing?
----------------------------------------------------------------------
Gary Richardson [gpr@agile.com]:
It's unclear whether you've tried this option or not:
Get the recompiled GCC and use that to compile a fresh GCC from source.
That's what I did in my Solaris env. This allowed me to get gcc
configured the way I wanted it and installed where I wanted it. From then on I was
able to compile all packages just fine.
So, I don't know if you tried this or not but if you didn't it might be
worth giving a shot.
Something else I just thought of that might be of help is that I "think"
you might need programs such as "ld" and "as" and possibly some others
to compile anything. I think they'd live in /usr/ccs/bin. Can't
remember. So if you do any compiling and get errors that you can't find these
programs, look there and make sure your path is set there. Otherwise
you could always grab the GNU binutils and compile that stuff. Just
a thought.
----------------------------------------------------------------------
Nikos George [nikos@jimmy.harvard.edu]:
I always get the binaries *only* to build a new gcc.
These are the steps I do :
./configure --prefix=/usr/local/gcc
make CC=gcc LANGUAGES=c
make stage1
make CC="stage1/xgcc -Bstage1/" CFLAGS="-g -O2" LANGUAGES="c"
make stage2
make CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O2" LANGUAGES="c"
make compare
make install CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O" LANGUAGES="c"
then you can pkgrm the binaries and use the compiled gcc from
/usr/local/bin
to build perl,...
make sure that /opt/bin (where the precompiled gcc lives) is in your
$PATH and /usr/ccs/... are towards the end!
----------------------------------------------------------------------
Nadya Williams [nadya@bog.ucsd.edu]:
You can use you ftp'ed binaries for gcc just to compile gcc from the
source. I believe you have to go only for stage1 and stage2 doing that, then
you can switch to the partially built coompiler (as of stage2) and finish you
gcc compilation and testing. When you build your gcc you set all the paths
the way you want. After the compilation just delete the ftp'ed package.
This is the way I did my gcc installation on new sun and it worked just
fine. Hope it helps.
----------------------------------------------------------------------
David S. Foster [foster@bial1.ucsd.edu]:
Once when I had this problem, another package was expecting the gcc
to be in one place but it was in another. I just created a link to gcc
where the package wanted to find it, and the problem was solved. Not
sure this will work in your situation.
I don't seem to recall in your first post you ever mentioning that
you "already get the precompiled packages there".
note: forwarded msg attached.
===
Ju
julienlim@rocketmail.com
_____________________________________________________________________
Sent by RocketMail. Get your free e-mail at http://www.rocketmail.com
attached mail follows:
I posted the following question earlier... and I've
had 2 people suggest getting the package from
sunsite.unc.edu... I just wanted to *reiterate* that
I did already get the precompiled packages there, and
it did install fine; however, it does not work when I
go and compile the Perl source because of the way the
precompiled package was built (paths are not set the
way I need them, and I'm unable to edit the
configurations used in the compilation process as
it's not readable). The bottom line is I *HAVE* to
build GCC (I can't use the readily available
packages), Perl, etc. 'cos we're doing quite a few
customizations in our company by adding libraries to
Perl that is only compilable using GCC (and it's not
possible with CC).
So, if anyone has any suggestions, I would be most
grateful if you could point me in the right
direction. Thanks.
Ju
---Ju-Lien Lim <julienlim@rocketmail.com> wrote:
>
> Does anyone know which libraries (Sun) are needed for
> me to build GCC-2.7.2 on Solaris 2.5.1?
>
> The reason I ask is 'cos I have a system that I
> inherited which doesn't have the complete O/S... and
> I've not been successful with building it so far.
> What I'm trying to do is to build it so that I can
> then build Perl using GCC (and not CC which works
> fine) and then build GD-1.14 which requires GCC etc.
> So I can't use any precompiled GCC or Perl (believe
> me... I've tried...)
>
> Thanks!
>
> Ju
> julienlim@rocketmail.com
>
_____________________________________________________________________
> Sent by RocketMail. Get your free e-mail at
http://www.rocketmail.com
>
>
_____________________________________________________________________
Sent by RocketMail. Get your free e-mail at http://www.rocketmail.com
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:06 CDT