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=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Yri1FkluL3epVV68Fq3UQfyPKY0brZDtFdemJ2lnVt4=; b=J34VROx3eYQyi92HS3CIkwvUTwrFfyZdxNJ9Sed6GskdAQrukuN+IiXsOtHM7iY5Lp wlduCFB/eDskXOXjp3iaGFwsvvYLH2o6pDBc6D60g0fH+06uQVOofc+gEroQwzSV65RS 8DxXrNYnXTF58V/c43oNKL0gQZmVKKUepgE2eK6NHgHD9jMjdK6vy0Kxs9lsD2rP0Y9j UneOWCPKcP/Eqq6lYIKzAnqXj9gVUfUjKzEZ9B8nbAhnf+sDP8O2xUo8qlD6dmhMK+sS n+wSHDOFISuJu/bF14VBDWh6v1eX6/mpBIVgtjfRpX/AQGo1ibk1ltGT9r3zNKRAatT4 xYqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Yri1FkluL3epVV68Fq3UQfyPKY0brZDtFdemJ2lnVt4=; b=PID8449Z+o8UIga8M/dSRFA2ilG/4dkKmAUvvLegrT/c3qAkyXqXhnzdGNa0FADzye Uu0yh0iGafZP5J5uyVUaZaflMOoaiGOpVJIsOf4t0eLlTTblNNIOOoWhwC0qWBX4cQi7 WgBC7g9TScnRy1aoBHVG7xV146wafm0Ni++dExW1pIxljRHDeNWTmcLlekL/gbMS1EId 3y/FTpMHJ+RljKCG++frPEoTiIaynByuYgOqkqqgs+pMXSehwgwlCgZmq+wyX6dIY6l+ FTKzPhYxzsj5CpLo/awUHFJ9bPhyR6JzgY9ImPT5muu6ySnumEH+zNiqdgojihb67JcP 0iWQ== X-Gm-Message-State: AOAM530WvBgczxKVPlaNBqlloetGDe+4O9bazv9iZVxcu0t9p6s5DV4m LCZzpdmvMbcz2SU9ABKPoaTNtA59qyxaQMwxM24otbkh8vjJEg== X-Google-Smtp-Source: ABdhPJy2DTmvg0BYeEEBbG0RUSFh2qBl3ACmiQqfS2BPoiYGXLksA6hf1zCWJPvzQq3CDoPWIsDFO7pVzKGYeyHOJj8= X-Received: by 2002:a67:7347:: with SMTP id o68mr10280976vsc.36.1629129491769; Mon, 16 Aug 2021 08:58:11 -0700 (PDT) MIME-Version: 1.0 References: <611a1807 DOT 1c69fb81 DOT d149c DOT 293bSMTPIN_ADDED_BROKEN AT mx DOT google DOT com> <611a8823 DOT 1c69fb81 DOT eb245 DOT e8eeSMTPIN_ADDED_BROKEN AT mx DOT google DOT com> In-Reply-To: <611a8823.1c69fb81.eb245.e8eeSMTPIN_ADDED_BROKEN@mx.google.com> From: "Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" Date: Mon, 16 Aug 2021 11:58:00 -0400 Message-ID: Subject: Re: [geda-user] pcb modules - are they actually used ? To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary="000000000000a66cb805c9af4452" Reply-To: geda-user AT delorie DOT com --000000000000a66cb805c9af4452 Content-Type: text/plain; charset="UTF-8" I'm not familiar with LTO, so I don't have a ready answer for related issues. I've never had trouble with pcb taking more than a few minutes to compile, even on older hardware. So, something is definitely wrong. If you provide the relevant information, I can try to reproduce the problem. It's perfectly possible to compile outside of the source tree, or in a dedicated build directory inside the source tree. I do this routinely. I believe you just have to run the configure script from wherever you want the build to be located. I have an example script that I can send when I get home if for some reason that doesn't work. It's possible that there's a flag or something that you have to specify. I haven't looked at it for a while. The build system has been around for a very long time and there are likely a lot of opportunities for improvement there. It's one of the items on my very long list of things to do. It's autotools that configures the use of environment variables such as LD when it generates the Makefiles. I don't believe that pcb makes any modifications to such variables. So, if the system is failing to respect their values, I would suspect that it's an issue with how something outside of pcb is set up. I haven't tried specifying an alternate linker before. On Mon, Aug 16, 2021 at 11:45 AM Branko Badrljica (brankob AT s5tehnika DOT net) [via geda-user AT delorie DOT com] wrote: > On Mon, 16 Aug 2021 15:09:27 +0000 > "Branko Badrljica (brankob AT s5tehnika DOT net) [via geda-user AT delorie DOT com]" > wrote: > > > > For example, fist LTO attempts failed for me UNTIL the first time > > I did full non-LTO compile and install. After that, LTO compiles and > > installs finish fine... > > > > Errrm. scratch that. I've borked CFLAGS /LDFLAG setting on later > attempts. LTO build never finishes fine. > > It looks like configure re-compiles ssconfig with LTO flags and > something gets badly broken in the process. > It also doesn't allow me to set different ld, with for example: > "LD=/usr/bin/ld.lld" > > ssconfig gets built in the same context as the application and library. > > --000000000000a66cb805c9af4452 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm not familiar with LTO, so I don't have a ready answer for = related issues. I've never had trouble with pcb taking more than a few= =20 minutes to compile, even on older hardware. So, something is definitely=20 wrong. If you provide the relevant information, I can try to reproduce the = problem.

It's perfectly possible to compil= e outside of the source tree, or in a dedicated build directory inside the = source tree. I do this routinely. I believe you just have to run the config= ure script from wherever you want the build to be located. I have an exampl= e script that I can send when I get home if for some reason that doesn'= t work. It's possible that there's a flag or something that you hav= e to specify. I haven't looked at it for a while.

The build system has been around for a very long time and there are= likely a lot of opportunities for improvement there. It's one of the i= tems on my very long list of things to do.

It&= #39;s autotools that configures the use of environment variables such as LD= when it generates the Makefiles. I don't believe that pcb makes any mo= difications to such variables. So, if the system is failing to respect thei= r values, I would suspect that it's an issue with how something outside= of pcb is set up. I haven't tried specifying an alternate linker befor= e.

= On Mon, Aug 16, 2021 at 11:45 AM Branko Badrljica (brankob AT s5tehnika DOT net) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
On Mon, 16 Aug 2021 15:09:27 +0000
"Branko Badrljica (brankob AT s5tehnika DOT net) [via geda-user AT delorie DOT com]"
<geda-user AT de= lorie.com> wrote:
>
> For example, fist LTO attempts failed for me UNTIL the first time
> I did full non-LTO compile and install. After that, LTO compiles and > installs finish fine...
>

Errrm. scratch that. I've borked CFLAGS /LDFLAG setting on later
attempts. LTO build never finishes fine.

It looks like configure re-compiles ssconfig with LTO flags and
something gets badly broken in the process.
It also doesn't allow me to set different ld, with for example:
"LD=3D/usr/bin/ld.lld"

ssconfig gets built in the same context as the application and library.

--000000000000a66cb805c9af4452--