From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2557 invoked by alias); 27 May 2005 13:35:23 -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 1990 invoked by uid 48); 27 May 2005 13:35:15 -0000 Date: Fri, 27 May 2005 13:37:00 -0000 Message-ID: <20050527133515.1988.qmail@sourceware.org> From: "papadopo at shfj dot cea dot fr" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050527123604.21782.papadopo@shfj.cea.fr> References: <20050527123604.21782.papadopo@shfj.cea.fr> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libffi/21782] configure: error: unknown endianess X-Bugzilla-Reason: CC X-SW-Source: 2005-05/txt/msg03571.txt.bz2 List-Id: ------- Additional Comments From papadopo at shfj dot cea dot fr 2005-05-27 13:35 ------- 1) I'm not sure this is a duplicate. The workstation I'm using is fully 64-bit functional: $ isainfo -v 64-bit sparcv9 applications 32-bit sparc applications $ Both gcc-3.4.4 and gcc-4.0.0 build fine without --disable-multilib. 2) This looks like a "regression" since --disable-multilib wasn't needed for earlier releases of gcc 3.3 on the same machine. 3) In any case, shouldn't this be detected while configuring gcc instead of later during the build process? -- What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|DUPLICATE | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21782