aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorRichard Biener <rguenther@suse.de>2023-01-23 11:14:05 +0100
committerRichard Biener <rguenther@suse.de>2023-01-23 11:19:00 +0100
commit47465fff9738b08796f4b52570fec49bbdbf3e57 (patch)
tree295eea201a25be11430b3167ef3da88f83e8a2cb /gcc
parent20552407ae11b61fccb46b3e96a8814e790254e7 (diff)
downloadgcc-47465fff9738b08796f4b52570fec49bbdbf3e57.zip
gcc-47465fff9738b08796f4b52570fec49bbdbf3e57.tar.gz
gcc-47465fff9738b08796f4b52570fec49bbdbf3e57.tar.bz2
modula2/108144 - fix mistake in previous change
The previous change to avoid a duplicate multi directory caused the m2/m2{cor,iso,log,min,pim} installs to happen relative to the main library directory when not using --enable-version-specific-runtime-libs which doesn't match the drivers expectation where to find them. The following fixes the original issue by simply dropping the duplicate multi directory since the one in the $(inst_libdir) variable now works. Tested by building and installing with and without --enable-version-specific-runtime-libs and compiling and linking a modula-2 testcase successfully with the installed compilers. PR modula2/108144 libgm2/ * libm2cor/Makefile.am: Revert previous change, instead drop the redundant $(MULTIDIR). * libm2iso/Makefile.am: Likewise. * libm2log/Makefile.am: Likewise. * libm2min/Makefile.am: Likewise. * libm2pim/Makefile.am: Likewise. * libm2cor/Makefile.in: Regenerate. * libm2iso/Makefile.in: Likewise. * libm2log/Makefile.in: Likewise. * libm2min/Makefile.in: Likewise. * libm2pim/Makefile.in: Likewise.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions