From: Anant S Athavale <asa@isac.gov.in>
To: gcc-help@gcc.gnu.org
Subject: Re: Problem compiling gcc 4.2.1 on AIX 5.3
Date: Mon, 28 Jan 2008 14:41:00 -0000 [thread overview]
Message-ID: <20080127085227.8E17910BC@dnserns.isac.gov.in> (raw)
In-Reply-To: <478F1A41.40608@cadenas.de>
Thanks everybody. Finally I could compile in full gcc 4.2.2 on AIX
5.3. It required me to install GNU bash and GNU bison to achieve it.
I ran normal configure without any options. And make went through.
It took several hours on my p610 system for to finish compiling.
Thanks a lot again for pointing me towards solving my problem.
Regards,
ANANT.
----- Message from T.Mittelstaedt@cadenas.de ---------
Date: Thu, 17 Jan 2008 10:05:05 +0100
From: Thomas Mittelstaedt <T.Mittelstaedt@cadenas.de>
Reply-To: Thomas Mittelstaedt <T.Mittelstaedt@cadenas.de>
Subject: Re: Problem compiling gcc 4.2.1 on AIX 5.3
To: Anant Athavale <asa@isac.gov.in>
Cc: gcc-help@gcc.gnu.org
> Anant,
>
> How did you configure gcc?
>
> I recently built version gcc 4.2.2 on aix 5.2 with the following configure
>
>
> ../gcc-4.2.2/configure --enable-version-specific-runtime-libs
> --enable-static --enable-shared --enable-threads
> --prefix=/opt/gcc-4.2.2 --without-gnu-ld --disable-nls --with-pic
> --disable-symvers --enable-symvers=no --enable-languages=c,c++,objc
>
> then built with:
> make CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2
> -fno-implicit-templates' bootstrap
>
> You may also consider to set environment variable CONFIG_SHELL to the
> full path of bash like
> CONFIG_SHELL=/usr/local/bin/bash
> At least when building on hp, it also proved to be useful to set CC to
> the full path of the bootstrap compiler like
> CC=/opt/gcc-3.2.1/bin/gcc
>
> Hope that gets you going. You also should use a gnu tar version higher
> than 1.13 to untar the sources and gnu make, of course.
> I used version 3.79.1.
>
> thomas
>
>
>
> Anant Athavale schrieb:
>> gcc compilation fails with the following error AIX 5.3
>>
>> ---------------------------------------------------------
>> make[3]: Entering directory `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/libiberty'
>> make[4]: Entering directory
>> `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/libiberty/testsuite'
>> make[4]: Nothing to be done for `all'.
>> make[4]: Leaving directory
>> `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/libiberty/testsuite'
>> make[3]: Leaving directory `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/libiberty'
>> make[3]: Entering directory `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/intl'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/intl'
>> make[3]: Entering directory `/tmp/gcc-4.2.1/build-powerpc-ibm-aix/libiberty'
>> make[4]: Entering directory
>> `/tmp/gcc-4.2.1/build-powerpc-ibm-aix/libiberty/testsuite'
>> make[4]: Nothing to be done for `all'.
>> make[4]: Leaving directory
>> `/tmp/gcc-4.2.1/build-powerpc-ibm-aix/libiberty/testsuite'
>> make[3]: Leaving directory `/tmp/gcc-4.2.1/build-powerpc-ibm-aix/libiberty'
>> make[3]: Entering directory
>> `/tmp/gcc-4.2.1/build-powerpc-ibm-aix/fixincludes'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory
>> `/tmp/gcc-4.2.1/build-powerpc-ibm-aix/fixincludes'
>> make[3]: Entering directory `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/zlib'
>> true "AR_FLAGS=rc" "CC_FOR_BUILD=gcc" "CFLAGS=-g
>> -fkeep-inline-functions" "CXXFLAGS=-g -O2" "CFLAGS_FOR_BUILD=-g
>> -O2" "CFLAGS_FOR_TARGET=-O2 -g -O2 "
>> "INSTALL=/tmp/gcc-4.2.1/install-sh -c"
>> "INSTALL_DATA=/tmp/gcc-4.2.1/install-sh -c -m 644"
>> "INSTALL_PROGRAM=/tmp/gcc-4.2.1/install-sh -c"
>> "INSTALL_SCRIPT=/tmp/gcc-4.2.1/install-sh -c"
>> "LDFLAGS=-Wl,-bbigtoc" "LIBCFLAGS=-g -fkeep-inline-functions"
>> "LIBCFLAGS_FOR_TARGET=-O2 -g -O2 " "MAKE=make"
>> "MAKEINFO=/tmp/gcc-4.2.1/missing makeinfo --split-size=5000000
>> --split-size=5000000 --split-size=5000000 " "PICFLAG="
>> "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" "EXPECT=expect"
>> "RUNTEST=runtest" "RUNTESTFLAGS=" "exec_prefix=/usr/local"
>> "infodir=/usr/local/info" "libdir=/usr/local/lib"
>> "prefix=/usr/local" "tooldir=/usr/local/powerpc-ibm-aix" "AR=ar"
>> "AS=as" "CC=gcc" "CXX=c++" "LD=ld" "LIBCFLAGS=-g
>> -fkeep-inline-functions" "NM=nm" "PICFLAG=" "RANLIB=ranlib"
>> "DESTDIR=" DO=all multi-do # make
>> make[3]: Leaving directory `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/zlib'
>> make[3]: Entering directory `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/libcpp'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/libcpp'
>> make[3]: Entering directory
>> `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/libdecnumber'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory
>> `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/libdecnumber'
>> make[3]: Entering directory `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/gcc'
>> make[3]: *** No rule to make target `all'. Stop.
>> make[3]: Leaving directory `/tmp/gcc-4.2.1/host-powerpc-ibm-aix/gcc'
>> make[2]: *** [all-stage1-gcc] Error 2
>> make[2]: Leaving directory `/tmp/gcc-4.2.1'
>> make[1]: *** [stage1-bubble] Error 2
>> make[1]: Leaving directory `/tmp/gcc-4.2.1'
>> make: *** [all] Error 2
>> ---------------------------------------------------
>>
>> I searched internet for the same, but some suggested use gnu tar to
>> untar the gcc source file.tar. Some said use gmake. Even after
>> using both, I getting this error.
>>
>> Please suggest how do I proceed. The system already has older
>> version of gcc installed ver 4.1.1.
>>
>> Regards,
>>
>> Anant Athavale.
>>
----- End message from T.Mittelstaedt@cadenas.de -----
Regards,
Anant Athavale,
Computer and Information Group,
ISRO Satellite Centre,
Airport Road,
Bangalore - 560017
INDIA.
Landline: 080-25083512
Cell: 99809 13616
My Free/BusyURL:
http://isacmail2.isac.dos.gov.in/kronolith/fb.php?u=asa%40isac.gov.in
next prev parent reply other threads:[~2008-01-27 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 19:27 Anant Athavale
2008-01-17 20:08 ` Thomas Mittelstaedt
2008-01-28 14:41 ` Anant S Athavale [this message]
2008-01-17 21:36 ` Kai Ruottu
2008-01-18 4:44 ` Anant S Athavale
2008-01-18 16:52 ` Anant Athavale
2008-01-18 18:32 ` Kai Ruottu
2008-01-18 19:07 ` Kai Ruottu
2008-01-19 12:30 ` Thomas Mittelstaedt
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=20080127085227.8E17910BC@dnserns.isac.gov.in \
--to=asa@isac.gov.in \
--cc=anant_athavale@yahoo.com \
--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).