From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: gcc-ddc Date: Thu, 23 Nov 2017 08:14:35 +0100 Message-ID: <87mv3dv59h.fsf@elephly.net> References: <871skskduj.fsf@gnu.org> <87lgj0wqbd.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36642) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eHlj0-00064F-6s for guix-devel@gnu.org; Thu, 23 Nov 2017 02:15:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eHliz-0000Ef-7Q for guix-devel@gnu.org; Thu, 23 Nov 2017 02:15:06 -0500 In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?utf-8?Q?G=C3=A1bor?= Boskovits Cc: Guix-devel Hi G=C3=A1bor, > I'm using the getenv approach Ricardo suggested. I've not written a wrapp= er > yet, the environment variables are set from the build. Maybe that=E2=80=99s sufficient already. Since the result of this package = is not going to be used as an input to build software it may not actually need a wrapper. Instead we can just set the variables in a build phase. > I'd like some help with choosing appropriate names for these environment > variables. I would prefix all of the environment variables with =E2=80=9CGUIX_GCC_=E2= =80=9D just to avoid conflicts with other legitimate environment variables. Other than that the names are fine. Thanks for investigating this. I=E2=80=99m impressed with your level of su= ccess! --=20 Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net