From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6434 invoked by alias); 4 Nov 2016 00:52:07 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 6260 invoked by uid 89); 4 Nov 2016 00:52:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=HTo:U*vapier, H*Ad:U*vapier, guidance, H*Ad:D*gentoo.org X-HELO: relay1.mentorg.com Date: Fri, 04 Nov 2016 00:52:00 -0000 From: Joseph Myers To: , Subject: Bootstrapping cross-toolchain for ia64 Message-ID: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2016-11/txt/msg00130.txt.bz2 The current cleanest approach for bootstrapping cross toolchains for GNU/Linux targets is (following the guidance at ): * Build binutils. * Install kernel headers. * Build static-only, C-only GCC, configured so that inhibit_libc is defined, and using --with-glibc-version so things like stack-smashing protection are correctly configured without glibc headers being available. * Build glibc, which should be identical to what you get from a longer sequence of alternating GCC and glibc builds (following fixes I made a few years ago for building like that with the initial bootstrap compiler). * Build GCC with shared libraries and C++ support. * If you want to run the glibc tests, you should reconfigure / rebuild with the new compiler to get everything required for all the tests. This doesn't work for ia64 because libgcc depends on system headers even with inhibit_libc. What's the cleanest approach (assuming recent-enough GCC and glibc) for building a cross toolchain for ia64-linux-gnu target, so I can make build-many-glibcs.py do whatever's necessary? -- Joseph S. Myers joseph@codesourcery.com