From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 101321 invoked by alias); 18 May 2017 01:10:14 -0000 Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org Received: (qmail 100185 invoked by uid 89); 18 May 2017 01:10:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=faced, deployed, 1132, wish X-HELO: mail-wm0-f44.google.com Received: from mail-wm0-f44.google.com (HELO mail-wm0-f44.google.com) (74.125.82.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 18 May 2017 01:10:12 +0000 Received: by mail-wm0-f44.google.com with SMTP id d127so34864615wmf.0 for ; Wed, 17 May 2017 18:10:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=vSJ0RLDiPdlJFuxtxsXzme1pIGAH8VbJ+KTXHEoJOFw=; b=nD2AOfmm5R/RI9zgcIF6AV8dx1Lxa2zK82VafauEZ3AeFkHKjU72t9YBVHcufsr3sS +hQSSppF7kYLIn+Spr7hgLvvRfBGm7exo0uioRr8iHZza/DIQuXHZGvt2rbKDU6gtwCu LnFed/92wBI1CrIP0Ijvk0ius7rotG3YgVyaSpvlhhnMMsYMaVfscswO9nz4nIVrpfvS zzzbXUErBYK+dBpYiQrK3Q3kJ7XMBwZib7+iHB8cChcR5zLtb8S6UEA3L4xGGlKRSKa+ iFVU316u+5mMuk2JE3E6ZyYFOSKm5l0YBODoV9wEalI4cI/FzifPv2sk9nBd+VzN/bKi SSZg== X-Gm-Message-State: AODbwcBUNl1AjEO29GxeRSeJ0Tc2uPlZBnbxh9amfqNrCXgoIE8HS+lA tgOtp2acfB7Y+KWutQ90KxbygH5Ify+j80o= X-Received: by 10.28.103.214 with SMTP id b205mr13641205wmc.126.1495069813342; Wed, 17 May 2017 18:10:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.134.197 with HTTP; Wed, 17 May 2017 18:10:12 -0700 (PDT) From: M D Date: Thu, 18 May 2017 01:10:00 -0000 Message-ID: Subject: Updating the Toolchain - sysroot update or building from scratch To: crossgcc@sourceware.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2017-05/txt/msg00003.txt.bz2 Hi, I had earlier built a cross compiler environment for an ARM based system using Crosstool-ng 1.13.2). This toolchain presently is configured with an earlier version of libc, libc2-11-1 and gcc-4-4-6.. I now wish to update the libc package in the Toolchain keeping the same compiler version at gcc-4-4-6. Two approaches come to my mind, the simpler one #1: Replace libc and the related libraries with the desired libc version in the sysroot directory. Also replace corresponding libc package header files at sysroot Result: I updated the sysroot with the libraries and headers and recompiled my applications against this toolchain. I deployed libc2-19 related libraries and the recompiled applications on the Filesystem. With some basic testing so far, things look good. The other approach is to build a fresh toolchain using a later version of Crosstool-ng and configuring for the desired version of libc, gcc etc. #2: Use crosstool-ng 1-20 with a later version of libc (libc2-19) and gcc at 4-4-6. I tried this approach but ran into a lot of issues. After a lot of debugging and adjusting the companion libraries, I still faced issues in the last stage related to libc. Question: Will approach #1 where we simply overwrite the libc (and other libraries like libpthread, libm, librt etc .. ) and the corresponding header files at the sysroot be a correct/valid way? Regards, Max