From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <crossgcc-return-23292-listarch-crossgcc=sources.redhat.com@sourceware.org>
Received: (qmail 17296 invoked by alias); 9 Aug 2018 05:03:27 -0000
Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <crossgcc.sourceware.org>
List-Subscribe: <mailto:crossgcc-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/crossgcc/>
List-Post: <mailto:crossgcc@sourceware.org>
List-Help: <mailto:crossgcc-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: crossgcc-owner@sourceware.org
Received: (qmail 17284 invoked by uid 89); 9 Aug 2018 05:03:27 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=BAYES_05,SPF_PASS autolearn=ham version=3.3.2 spammy=HTo:U*crossgcc, downloads, Hx-languages-length:552, Toolchain
X-HELO: smtp5.epfl.ch
Received: from smtp5.epfl.ch (HELO smtp5.epfl.ch) (128.178.224.8) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 09 Aug 2018 05:03:24 +0000
Received: (qmail 24790 invoked by uid 107); 9 Aug 2018 05:03:20 -0000
Received: from unknown (HELO [192.168.43.24]) (213.55.176.161) (TLS, ECDHE-RSA-AES256-GCM-SHA384 (X25519 curve) cipher) (authenticated)  by mail.epfl.ch (AngelmatoPhylax SMTP proxy) with ESMTPSA; Thu, 09 Aug 2018 07:03:20 +0200
X-EPFL-Auth: 31jxPW16S2wsszsV2+gVm5mtbfRagb+alSBtGVqQ9Qnzo0Yeb60=
To: crossgcc@sourceware.org
From: Roosembert Palacios <roosembert.palacios@epfl.ch>
Subject: Building ESP32 Toolchain in NixOS (Crosstool-NG)
Message-ID: <76c3f2d7-5100-fb6b-6396-73f2db365a41@epfl.ch>
Date: Thu, 09 Aug 2018 05:03:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2018-08/txt/msg00000.txt.bz2

Hello,

I'm packaging Espressif's ESP32 toolchain on nixos (WIP: 
https://gitlab.com/roosemberth/dotfiles/blob/master/nixos-config/pkgs/esp32-toolchain/default.nix) 
due to it's nature, all inputs must be made explicit in the package 
definition. However, it seems ct-ng downloads some libraries when 
building. Nixos packages build in an isolated sandbox with access only 
to the declared sources and package dependencies.

Is there a way to list and provide such requirements?

Bests,
Roosembert Palacios