On 08.07.19 23:19, Matthias Klose wrote: > On 14.06.19 15:09, Gaius Mulley wrote: >> >> Hello, >> >> here is version two of the patches which introduce Modula-2 into the >> GCC trunk. The patches include: >> >> (*) a patch to allow all front ends to register a lang spec function. >> (included are patches for all front ends to provide an empty >> callback function). >> (*) patch diffs to allow the Modula-2 front end driver to be >> built using GCC Makefile and friends. >> >> The compressed tarball includes: >> >> (*) gcc/m2 (compiler driver and lang-spec stuff for Modula-2). >> Including the need for registering lang spec functions. >> (*) gcc/testsuite/gm2 (a Modula-2 dejagnu test to ensure that >> the gm2 driver is built and can understands --version). >> >> These patches have been re-written after taking on board the comments >> found in this thread: >> >> https://gcc.gnu.org/ml/gcc-patches/2013-11/msg02620.html >> >> it is a revised patch set from: >> >> https://gcc.gnu.org/ml/gcc-patches/2019-06/msg00220.html >> >> I've run make bootstrap and run the regression tests on trunk and no >> extra failures occur for all languages touched in the ChangeLog. >> >> I'm currently tracking gcc trunk and gcc-9 with gm2 (which works well >> with amd64/arm64/i386) - these patches are currently simply for the >> driver to minimise the patch size. There are also > 1800 tests in a >> dejagnu testsuite for gm2 which can be included at some future time. > > I had a look at the GCC 9 version of the patches, with a build including a > make > install. Some comments: > > - A parallel build (at least with -j4) isn't working. A sequental > build works fine. I think forcing a sequential build will not > work well, increasing the build time too much. > > - libgm2 multilib builds are not working. <builddir>/<target>/32/libgm2 > is configured, but not built. > > - The internal tools in the gcclibdir are installed twice, with > both vanilla names and prefixed/suffixed names. > > - libgm2/configure.a has a libtool version 14:0:0, however all > shared libraries are installed with soversion 0. > > - no manual page for gm2m. > > - libpth.{a,so} is installed in the system libdir, which > conflicts with the installation of the libpth packages > on most distros. > > - There are three letter libraries with pretty generic > names installed into the system libdir: log, iso, cor, > min, ulm. At least for log, you have a file conflict > with another library. Shouldn't these libraries named > mpre specific, like libgm2log? > > Matthias > > The installed tree:
> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/ulm/libulm.a > ./usr/lib/x86_64-linux-gnu/libulm.a and all static libraries are installed twice, not just libulm.a. What is the correct location? Matthias
