From: Rene Salmon <rsalmon@tulane.edu>
To: gcc-help@gcc.gnu.org
Subject: compile problem gcc-3.4.4 with -maix64 on aix 5.3
Date: Tue, 12 Jul 2005 17:04:00 -0000 [thread overview]
Message-ID: <42D3F7EB.80601@tulane.edu> (raw)
Hi,
We are trying to compile gcc-3.4.4 with -maix64 on aix 5.3. here is the
setup:
We are using the 32bit gcc 3.3.2 rpm binaries that are available from
IBM to do this.
setenv make /opt/freeware/bin/make
setenv CONFIG_SHELL /opt/freeware/bin/bash
setenv CFLAGS -maix64
setenv CC /opt/freeware/bin/gcc
cd objectdir/
../gcc-3.4.4/configure --prefix=/usr/local/opt/gcc-3.4.4 --with-
as=/usr/bin/as --with-ld=/usr/bin/ld --disable-nls
--enable-languages=c,c++ --en
able-threads --enable-version-specific-runtime-libs
After this is done I edit the Makefile created in objectdir to add these
lines so that the libs created are 64bit.
AR = ar -X64
AR_FLAGS = rc
RANLIB = ranlib -X64
The I do a make but it fails with a message about missing symbols in
libiberty/libiberty.a. The symbols are there I checked so I think that
the problem is just the the libiberty.a just is in the wrong format.
Any ideas as to how to fix this? Here is the error message.
/opt/freeware/bin/make bootstrap
HEADERS="config/rs6000/rs6000.h config/rs6000/aix.h
config/rs6000/aix52.h config
/rs6000/xcoff.h defaults.h" DEFINES="" \
/opt/freeware/bin/bash ../../gcc-3.4.4/gcc/mkconfig.sh tm.h
TARGET_CPU_DEFAULT="" \
HEADERS="auto-host.h ansidecl.h" DEFINES="" \
/opt/freeware/bin/bash ../../gcc-3.4.4/gcc/mkconfig.sh bconfig.h
/opt/freeware/bin/gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prot
otypes -Wmissing-prototypes -pedantic -Wno-long-long -DHAVE_CONFIG_H
-DGENERA
TOR_FILE -I. -I. -I../../gcc-3.4.4/gcc -I../../gcc-3.4.4/gcc/.
-I../../gcc-3.
4.4/gcc/../include ../../gcc-3.4.4/gcc/genmodes.c -o genmodes.o
/opt/freeware/bin/gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prot
otypes -Wmissing-prototypes -pedantic -Wno-long-long -DHAVE_CONFIG_H
-DGENERA
TOR_FILE -I. -I. -I../../gcc-3.4.4/gcc -I../../gcc-3.4.4/gcc/.
-I../../gcc-3.
4.4/gcc/../include ../../gcc-3.4.4/gcc/errors.c -o errors.o
/opt/freeware/bin/gcc -g -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototy
pes -Wmissing-prototypes -pedantic -Wno-long-long -DHAVE_CONFIG_H
-DGENERATOR
_FILE -o genmodes \
genmodes.o errors.o ../libiberty/libiberty.a
ld: 0711-317 ERROR: Undefined symbol: .xmalloc
ld: 0711-317 ERROR: Undefined symbol: .htab_find_slot
ld: 0711-317 ERROR: Undefined symbol: .htab_hash_string
ld: 0711-317 ERROR: Undefined symbol: .xstrdup
ld: 0711-317 ERROR: Undefined symbol: xcalloc
ld: 0711-317 ERROR: Undefined symbol: .htab_create_alloc
ld: 0711-317 ERROR: Undefined symbol: .htab_find
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
information.
collect2: ld returned 8 exit status
make[2]: *** [genmodes] Error 1
make[2]: Leaving directory `/usr/local/src/objdirgcc64/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/usr/local/src/objdirgcc64/gcc'
make: *** [bootstrap] Error 2
Thank you
Rene
--
-
--
Rene Salmon
Tulane University
Center for Computational Science
Richardson Building 310
New Orleans, LA 70118
http://www.ccs.tulane.edu
Tel 504-862-8393
Fax 504-862-8392
reply other threads:[~2005-07-12 17:04 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=42D3F7EB.80601@tulane.edu \
--to=rsalmon@tulane.edu \
--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).