From owner-freebsd-bugs@FreeBSD.ORG Thu Aug 19 21:38:23 2010 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 193D610656AA; Thu, 19 Aug 2010 21:38:23 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E2BF18FC08; Thu, 19 Aug 2010 21:38:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o7JLcMPG037625; Thu, 19 Aug 2010 21:38:22 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o7JLcMr1037621; Thu, 19 Aug 2010 21:38:22 GMT (envelope-from arundel) Date: Thu, 19 Aug 2010 21:38:22 GMT Message-Id: <201008192138.o7JLcMr1037621@freefall.freebsd.org> To: pgollucci@FreeBSD.org, arundel@FreeBSD.org, freebsd-bugs@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: bin/139146: gcc(1): gcc -m32 doesn't quite work X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Aug 2010 21:38:23 -0000 Synopsis: gcc(1): gcc -m32 doesn't quite work State-Changed-From-To: open->suspended State-Changed-By: arundel State-Changed-When: Thu Aug 19 21:19:26 UTC 2010 State-Changed-Why: Judging from the various threads on freebsd-amd64@, fixing this issue is non- trivial and requires some fundamental changes to gcc's include and linker search paths. Petter Wemm provided a patch in [1], but at the same time states that the patch doesn't fix the issue properly. Apart from him most of the developers seem to have abandoned the idea of fixing/discussing this issue: "Short summary: it never worked and will not work unless some non-trivial work is put into how GCC handles include and linker search paths." - Alexander Kabaev Thus suspend this PR for now. Everyone is welcome to work on this problem. However please gather information from the various freebsd mailinglists dealing with this issue BEFORE creating a new thread, unless you are prepared to making new enemies. ;) [1] http://lists.freebsd.org/pipermail/freebsd-amd64/2008-December/011775.html http://www.freebsd.org/cgi/query-pr.cgi?pr=139146