From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from host02.dmghosting.com (host.dmghosting.com [69.16.219.106]) by sourceware.org (Postfix) with ESMTPS id B6F8D3858D35 for ; Mon, 31 Aug 2020 01:53:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B6F8D3858D35 Received: from cpe-71-65-85-222.cinci.res.rr.com ([71.65.85.222]:60322 helo=forge.silogroup.lan) by host02.dmghosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1kCZ0s-0004NZ-Oa for crossgcc@sourceware.org; Sun, 30 Aug 2020 21:53:39 -0400 Message-ID: Subject: x86_64 cross-compiler From: Chris Punches To: crossgcc maillist Date: Sun, 30 Aug 2020 21:53:38 -0400 Organization: SILO GROUP, LLC Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host02.dmghosting.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - silogroup.org X-Get-Message-Sender-Via: host02.dmghosting.com: authenticated_id: chris.punches@silogroup.org X-Authenticated-Sender: host02.dmghosting.com: chris.punches@silogroup.org X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: crossgcc@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: crossgcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2020 01:53:40 -0000 Has anyone gotten an x86_64 cross-compiler successfully built with crosstool-ng? If you did, would you mind providing your config? The samples do not appear to work for various reasons. My intent is to build a cross-compilation toolchain to `/opt/cross-compiler`, and then build a native (multilib) compiler toolchain at `/opt/compiler`. From there I'd like to use `/opt/compiler` to populate a chroot. It sounds pretty simple, but, I could use some guidance as it is turning out to be anything but. -C