From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27591 invoked by alias); 23 Dec 2004 18:22:38 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 27524 invoked by uid 48); 23 Dec 2004 18:22:31 -0000 Date: Thu, 23 Dec 2004 18:22:00 -0000 Message-ID: <20041223182231.27523.qmail@sourceware.org> From: "hjl at lucon dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041223004714.19135.janis187@us.ibm.com> References: <20041223004714.19135.janis187@us.ibm.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug bootstrap/19135] [4.0 Regression] build failure in libiberty multilibs X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg03367.txt.bz2 List-Id: ------- 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