Hi Thomas, this patch looks very similar to previous ones. I therefore deem it ok for mainline. May be you want to wait for Jerry to voice his ok/findings before you apply it.
Thanks for the patch. - Andre On Sun, 6 Oct 2024 08:58:30 -0700 Jerry Delisle <jvdelis...@gmail.com> wrote: > The iparm.m4 was what I was looking for. Thanks, > > Jerry > > On Sun, Oct 6, 2024, 5:26 AM Thomas Koenig <tkoe...@netcologne.de> wrote: > > > Am 05.10.24 um 22:52 schrieb Thomas Koenig: > > > Hi Jerry, > > > > > >> I see all the generated files in the patch, but I do not see the M4 > > >> macro or other mechanism which generated these. Was this in a > > >> previous submission that I missed? > > > > > > The "magic" in this case is mentioning them in Makefile.am and > > > (regenerated) in Makefile.in. > > > > > > The rest is done by the previous modification to m4/iparm.m4 in > > > 5d98fe096b5d17021875806ffc32ba41ea0e87b0 , which generates > > > the type from the file name, in this case containing the 'm' > > > as the type-specifying letter. > > > > To be a little bit more elaborate... > > > > Since the patch which removed some machinery warnings, you have to use > > --enable-maintainer-mode (and do the above). The generated files will > > then be in (assuming your build directory is trunk/bin and the > > architecture is AMD64 on Linux) > > trunk-bin/x86_64-pc-linux-gnu/libgfortran/generated > > and you then have to copy what's new over to > > trunk/libgfortran/generated , then do a second bootstrap, preferably in > > a separate directory) without --enable-maintainer-mode to see if > > everything works right. > > > > Best regards > > > > Thomas > > > > > > -- Andre Vehreschild * Email: vehre ad gmx dot de
