[Bug bootstrap/50229] [4.8/4.9/5 Regression] Can't cross compile for i686-apple-darwin10 from x86_64-redhat_linux

["iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50229

--- Comment #21 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Francois-Xavier Coudert from comment #20)
> This PR appears to report two different issues:
>   1. cross-compiler targeting Darwin

cross-compilers targeting Darwin <= 9 are possible using odcctools.

For "the future"
I am working on a set of GCC patches and a GAS port that solves part of the
problem for newer cases.  I intend to post these before stage#1 ends (but time
is short - esp. with trunk trashed on darwin at the moment).

However the static linker remains an issue (I have a build of ld64-127.2 which
supports Darwin10, and ppc*) … however, this needs to be forward-ported to the
latest published sources for ld64 before it will support "current" Darwin.  

In any event, it would be the User's responsibility to obtain a suitable SDK
for the target - by downloading the appropriate Xcode and extracting the SDK as
needed.

in short: "can't be expected to work until there's a set of Darwin 'binutils'
supporting > darwin 9". (working on providing that).

>   2. cross-compiler hosted on Darwin

I do this all the time - it's possible to cross from x86_64-darwin12 ->
powerpc-darwin9, for example (assuming one has the relevant cctools and ld64,
and enough patience).

I have also built native-crosses [x86-64-darwin12=build powerpc-darwin8
host/target] for the record.

Darwin works just fine as a host for cross-compilers to Linux.

(building your own sysroot - in particular GLIBC can be a trial, but if you
make a sysroot from a standard distro, it's not hard).

in short (2) is very definitely "works for me"
>From gcc-bugs-return-466067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 08 18:11:34 2014
Return-Path: <gcc-bugs-return-466067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26468 invoked by alias); 8 Nov 2014 18:11:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26427 invoked by uid 48); 8 Nov 2014 18:11:31 -0000
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libitm/63781] potential linkage issue with libitm.1.dylib
Date: Sat, 08 Nov 2014 18:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libitm
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: howarth at bromo dot med.uc.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63781-4-m9bF3Aa0i9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63781-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63781-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg00539.txt.bz2
Content-length: 361

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc781

--- Comment #2 from howarth at bromo dot med.uc.edu ---
The missing linkage on libstdc++ would be solved by making sure that the
/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/./gcc/xg++ compiler is used
to link libitm rather than the current
/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/./gcc/xgcc.