X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to; s=fm2; t=1689203530; x=1689289930; bh=fX ZHbRQ6KGZfZ7rIWDbN1Xmd2JaHxlZ7DIVk3pHhXsQ=; b=kYRbn3Vj1XhtkKKUAv 3ZryMVD2aRvvlWVB0sDhFy42O2AzKeZnoTYN0+CqUuFDOyWzwtnegutRJ2dONoIk jZzGqzthknj1+y2AZsqjzSZZxYa6rBr2Y+ucv/xlkw0bIm/EnD4VUu7GoLT7xsY6 ek6MxtdvdL0ERQEGRMsy3koBrn23DETsu7zZvTjJ7+U6y5WWWYhj38dA6On5Wouu Agf741DTE7H8eE53xST7brjJxsDK75Fi5kGzyB2aJXN38s+YbtvkOxUJCIGwAJv/ jrS6RfR7Znx1sVz/9N47fT8QdHrpYXJS9rI/TC10ohYSD02XyAgYvEGWxNd5bVsh rzzA== X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1689203530; x=1689289930; bh=fXZHbRQ6KGZfZ 7rIWDbN1Xmd2JaHxlZ7DIVk3pHhXsQ=; b=NjzReXzxzyRM8ZXPyn164pnxJAcbK rq0LToXdnU/k+oujhm0is+mmMCyXaKfEzIYo9fTrNbmdqryrHXnXQCBidMz0/R/t G1egoXaR9Lj6+EIblX6VR3CEcUg9SLOBQeg+az2S0U/bfk8Bylvp5vFhvvPjnTuo xiekB+RyI78ByrW4JW8hNRCQ+btbP8ac+9+37bjSo6tTPlNR19RDO7jQQWaxPIK9 VKZ9bh4MPTe3AgJLNeV6RTG2oj6eX+OlwlzOj45SMHG1DCpezvVDUb2Vfy0DGCCw piIFftuyoIJ7Bp6uE+c4Y2q1gIZOKJqFb9RO606dmzw9FIy8N52EXj7gg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrfeefgddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfvhffutgfgsehtkeertddtfeejnecuhfhrohhmpefiihhrvhhinhcu jfgvrhhruceoghhhvghrrhhlvdesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrghtth gvrhhnpeeuheeifffgtedvgfdvieevtddttdehkeffteffieegheefgefhleeutddugfef tdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehghh gvrhhrlhdvsehfrghsthhmrghilhdrtghomh X-ME-Proxy: Feedback-ID: iee494631:Fastmail Message-ID: <968ccc54-0513-8444-1944-5f98c662eaf2@fastmail.com> Date: Wed, 12 Jul 2023 16:10:23 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.2 Content-Language: en-US To: gEDA User Mailing List From: "Girvin Herr (gherrl2 AT fastmail DOT com) [via geda-user AT delorie DOT com]" Subject: [geda-user] geda-gaf 1.10.2 make check test failure Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Reply-To: geda-user AT delorie DOT com I am building geda-gaf 1.10.2 on my Slackware64 15.0 system for the first time. It is my policy to build a package twice - once in a user mode corral to make sure the program builds without going out and trying to change root-privileged files on my disk and then if it builds fine there, I go on to build in root for installation. This geda-gaf version built fine in user mode with "make check", but when I build in root, I am getting a fatal test error:     "unit-tests/t0402-config.scm" Just the one error that I can tell. It appears to pass all the other tests. I remember there were "make check" test failures with geda-gaf in the past and the solution then was to ignore them by not doing the make check, but are these failures still present? I thought they got fixed (regression?). In order to keep things moving along, I am disabling the make check, but I don't think that is the solution. Is this a known problem and is disabling the make check the best way to get geda-gaf up and running on my machine? Also, an unrelated problem is that a while back there was a problem using scripts in /etc/profile.d to set the GEDADATA* environment variables. Something about causing lepton-eda to fail if they are used. Is this still a problem or can I automate this process again? Here is the note I made in my package notes document for 1.10.2 on the Slack32 14.2 system: "The two profile scripts are no longer installed into "/etc/profile.d". These two scripts are "geda.sh" and "geda.csh". They set the GEDADATA* environment variables so that the users don't have to do so. However, these files can interfere with the lepton-eda suite, so are no longer automatically installed. ... " The root build with "make check" disabled ran to the end without any errors. So the workaround to get geda-gaf running is to disable make check, but... Thanks. Girvin Herr