On Tue, 4 Mar 2025 00:08:16 +0100 Jakub Jelinek <ja...@redhat.com> wrote:
> On Mon, Mar 03, 2025 at 05:21:38PM -0500, James K. Lowden wrote: > > However IMO, the incantation: > > > > make install DESTDIR=/foo > > > > is invalid. The compiler's library search path is fixed when the > > compiler is built, based on configure options. Installing into an > > arbitrary directory cannot work; there is no opportunity then to > > alter the gcobol binary. > > This is how most distros install stuff for their packaging systems, > make install DESTDIR=/some/directory > and then everything under /some/directory > is packaged into the package. > GCC is generally relocatable, the compiler driver should find the > compiler and library/include directories etc. relative to where the > driver resides in the filesystem. Thank you for taking the time to explain that, Jakub. I stand corrected, and I believe you'll find that DESTDIR works as intended using the current cobol-patched branch. It works here for me. Somehow, despite reading the automake documentation over and over these last several days while we struggled to bring the libgcobol build process into the 20th [sic] century, I didn't put 2 + 2 together. Looking at it now, I see that by using automake we get DESTDIR for free, provided (as we do) that we use libtool for installation. In short, despite not trying to support DESTDIR, we do anyway, by happy accident. And we are now better informed. Regards, --jkl
