BTW: > On Jul 2, 2021, at 9:45 AM, Barry Smith <[email protected]> wrote: > > NPS WARNING: *external sender* verify before acting. > > >> On Jul 2, 2021, at 10:03 AM, Stefano Zampini <[email protected]> >> wrote: >> >> Patrick >> >> Should this be fixed in PETSc build system? >> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJuliaPackaging%2FYggdrasil%2Fblob%2Fmaster%2FP%2FPETSc%2Fbundled%2Fpatches%2Fpetsc_name_mangle.patch&data=04%7C01%7Cjekozdon%40nps.edu%7Ce30e522e78d643e61c7d08d93d78ddf7%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637608411608120561%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=q1T617kzxD9HsSoXQTl7N%2FRi%2B%2BoKHbOgZRy7KEnmZKY%3D&reserved=0 > > This line worries me. > > How does the get work here? If the first argument is a list while the > second seems to be a (n empty) string then what will the [0] do with the > empty string? It seems possible the use of get in Configure has to be double > checked everywhere it is used to ensure consistency between whether a list or > some other type is returned. Perhaps a custom "get" is needed for configure > to make the code clean and always handle lists etc properly? > > Barry
For the Julia build it's unclear to me why this was put in the original build script since configure option is --with-blaslapack-suffix="" which seems to just be the default anyway(?)
