From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20056 invoked by alias); 13 Mar 2019 18:47:45 -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 20044 invoked by uid 89); 13 Mar 2019 18:47:44 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=3.6 required=5.0 tests=BAYES_00,CROSSGCC_BAD,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=fritz, HX-Languages-Length:784, aiming X-HELO: mail-it1-f171.google.com Received: from mail-it1-f171.google.com (HELO mail-it1-f171.google.com) (209.85.166.171) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 13 Mar 2019 18:47:43 +0000 Received: by mail-it1-f171.google.com with SMTP id 188so555990itb.0 for ; Wed, 13 Mar 2019 11:47:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=NpnH+hbukN6OQq279w45zM+OjhJndAmVlBDHl2NPg6w=; b=I1gZCtE9efSh+JMXbS2Fnni73qCaDfpFuyPNnnqtS1RoWVe+JHfiBYTJW/WkpHUOJr wZ1xuTxTMCDS6/KgpW0+pmiW+uE973JFEgCNxWTrtRJm5ytAMnYQeoG0Cgb2vnWoZxuq MPf8F3kBvggqDZxylvgaEU30CeERA5/Nz4124oeYBb7d7M9hpMpWkr6U5MOwFgmaeOhb BGC9dON0yB0g1h6TFYKNjiJ7k0cPiObH6/A4gU3kRFlZOZVeHqupS07PQy9mypeWjzKN ceeW+L8gp3+A0vuc5Uf9eyOL7nueJrbZJ1pO+nTpfowb3UsEip+MzgJBtV0b5LFUPMh2 Wiig== MIME-Version: 1.0 Received: by 2002:a02:3205:0:0:0:0:0 with HTTP; Wed, 13 Mar 2019 11:47:41 -0700 (PDT) From: Fritz Reese Date: Wed, 13 Mar 2019 18:47:00 -0000 Message-ID: Subject: Programs missing or too old: python make bison To: crossgcc@sourceware.org Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-03/txt/msg00008.txt.bz2 Hello all, I am hoping someone can set me straight here. When attempting to build a cross-compiler toolchain, the configure step for glibc finds my system versions of python, make, and bison too old, and bails out. I am not surprised because I am aiming to build a much newer kernel/glibc than I have on my build/host system. However, I thought ct-ng would build these support tools for me (at least make) and use the correct versions for the build. Am I mistaken, or did I configure the build improperly? In either case how do I control the version of make ct-ng is using to build? Can I tell it to use the fancy new make it is already building for me, or do I need to build make myself and set it first in my PATH? Cheers, Fritz