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=gmail.com; s=20210112; t=1679431817; h=mime-version:message-id:in-reply-to:date:subject:to:user-agent :references:from:from:to:cc:subject:date:message-id:reply-to; bh=jWPiTbmBgdmOOYsBbCHen3cfJ1beqVUwZSG5QRfrETM=; b=Btge5P/LEhZXo8DSsunqOzh+q7aD4fXFUQau0KO0BW96W4SZl6ajpCARpROSpJnQ8o MHnhQmjqlr2huQ7DNnCgAMQNjYDOZZLawMd5GyCD/mEzSbfbFaogcWiUZXNJsBwL2r/O Uh1wL6AT0/CW+VpgGp1FPLMnJSxSRmBvp0uY/b2+4m+cXnLKtI/5j9pqL5nct2JPwZaO h7786nzRH95KuzHREEfR0DCAJyCeT+7kgpKtFDt9pjE15bnGgmPVd9OX++fxHDdYDuak sUgmjBIvBB3m9+JdIjZQP1/Ysje2SZZESzO4emSjAVsC5sX7Hx0SycTWZn+C83yNErgy 4cxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679431817; h=mime-version:message-id:in-reply-to:date:subject:to:user-agent :references:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=jWPiTbmBgdmOOYsBbCHen3cfJ1beqVUwZSG5QRfrETM=; b=CZ6wWcTlWqF4fnuI5J5QK/2xTHbX1VdJAUtRSv5LNgNhhn+WQvC0CH7GshEkey1OV0 AqEtA7whzSJZ9Wk+Urki2HiqI7zStQioZRC+u5fSo2zeniNHEUQMLUX0cV53kg5Pnlm6 C6KbcW7lBpoHy4ke+g64azUzcJ7WH4C0k0r70RmNePcvqjeLsLv2SZldyGkRaiep8pE+ OizE5CtGh5RBC4bbydHmSl4UQX4IY73sNJGsogqKSSS8YnCjLs722FO+NMk0RqHRwMNM tHUAH+2ZHWcFCmJdnI9mQTjf4Vuz3lcgduzJ7EFLihrgcNc1MVCwwMF2qRWRxGyJn1Za apdw== X-Gm-Message-State: AO0yUKWsZxeZbrAVRcesGccw/OkcBDNao7pMlhYFDg5KqL0hXgWOi2MF cp/fsJ+5JmBhUhvM7xDB20TjxMmtybs= X-Google-Smtp-Source: AK7set87iQTpm7rQe+9ghKn7BwZp6EChlJY7vb0PiLzb9f4u5NE1udJW44lNNlavZlMb9p1JXiM+AQ== X-Received: by 2002:a2e:9e8a:0:b0:295:ab86:336b with SMTP id f10-20020a2e9e8a000000b00295ab86336bmr1301483ljk.15.1679431817254; Tue, 21 Mar 2023 13:50:17 -0700 (PDT) From: "vzh (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" X-Google-Original-From: vzh References: <20230319121903 DOT 84DEA8497641 AT turkos DOT aspodata DOT se> User-agent: mu4e 1.8.11; emacs 28.2 To: geda-user AT delorie DOT com Subject: Re: [geda-user] lepton-sch2pcb: wrong ${prefix} for pcb Date: Tue, 21 Mar 2023 23:33:25 +0300 In-reply-to: <20230319121903.84DEA8497641@turkos.aspodata.se> Message-ID: <87ttydx20n.fsf@lepton.mail-host-address-is-not-set> MIME-Version: 1.0 Content-Type: text/plain Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk "karl AT aspodata DOT se [via geda-user AT delorie DOT com]" writes: > For: > $ git branch -v > * (HEAD detached at vzh/sch2pcb-rewrite-sch2pcb-add-elements-in-scheme) 60d7148f0 sch2pcb: Rewrite sch2pcb_add_elements() in Scheme. > > running lepton-sch2pcb doesn't find pcb's common.m4: > $ lepton-sch2pcb styrkort.sch > ... > gsch2pcb backend configuration: > > ---------------------------------------- > Variables which may be changed in gafrc: > ---------------------------------------- > gsch2pcb:pcb-m4-command: "/usr/bin/m4" > gsch2pcb:pcb-m4-dir: "/usr/local/share/pcb/m4" > gsch2pcb:pcb-m4-path: ("$HOME/.pcb" ".") > gsch2pcb:m4-files: "" > > --------------------------------------------------- > Variables which may be changed in the project file: > --------------------------------------------------- > gsch2pcb:use-m4: yes > > ---------------- > M4 command line: > ---------------- > /usr/bin/m4 -d -I/usr/local/share/pcb/m4 -I$HOME/.pcb -I. /usr/local/share/pcb/m4/common.m4 - > > ===================================================== > Using the m4 processor for pcb footprints > /usr/bin/m4: cannot open `/usr/local/share/pcb/m4/common.m4': No such file or directory > ... > > m4 is looing in the wrong place: > $ ls -l /usr/share/pcb/m4/common.m4 > -rw-r--r-- 1 root root 3718 Feb 3 2019 /usr/share/pcb/m4/common.m4 > $ ls -l /usr/local/share/pcb/m4/common.m4 > ls: cannot access '/usr/local/share/pcb/m4/common.m4': No such file or directory > $ > > > Can it be that configure assumes the same ${prefix} for both lepton > and pcb: It looks like this is true. A similar issue wrt geda-gaf has been discussed recently on the list: https://delorie.com/archives/browse.cgi?p=geda-user/2023/03/13/17:27:56 I imagine two ways to solve / work around it: - Find out a reliable command (possibly several commands) that would define pcb m4 path at the run time. - Add a config key to override the path set by configure. (Not sure if configure has to look up for it at all.) E.g. "m4-path" in the group "[sch2pcb]". WDYT? Regards, Vladimir