This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/19135] [4.0 Regression] build failure in libiberty multilibs
- From: "hjl at lucon dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 Dec 2004 18:22:31 -0000
- Subject: [Bug bootstrap/19135] [4.0 Regression] build failure in libiberty multilibs
- References: <20041223004714.19135.janis187@us.ibm.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From hjl at lucon dot org 2004-12-23 18:22 -------
With the new patch, there are
COMPILER = $(CC) @DEFS@ $(LIBCFLAGS) $(HDEFINES) @ac_libiberty_warn_cflags@
COMPILE.c = $(COMPILER) -c -I. -I$(INCDIR)
LTCOMPILE = $(LIBTOOL) --mode=compile $(COMPILE.c)
LINK = $(LIBTOOL) --mode=link $(COMPILER)
Unless LINK is overriden somehow, the same command should be used to compile
64bit object file and build 64bit shared library. If -m64 is used to
compile 64bit object file, -m64 should also be used to build 64bit shared
library. Can you show me the output of
# cd 64bit target libiberty
# rm -f xexit.lo
# cd 32bit target libiberty
# rm -f xexit.lo
# make
I'd like to see how 32bit and 64bit object files and libraries are built.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19135