"Gabriel Staples, ElectricRCAircraftGuy.com" <erca...@gmail.com> writes:
> Thanks, Niels. I had been looking in config.log and came across a failure > to include a file with an absolute path. I found the solution and wrote > about it here: https://stackoverflow.com/a/77435216/4561887 I've had a quick look, but really too long for me to read carefully. And please avoid calling other peoples work ugly things like "stinky". If needed, please calm down before posting stuff. Can you explain concisely in which way absolute include paths made gmp configure break in your environment? It's not clear to me why gmp's configure would ever attempt to compile anything with an #include "/c/foo/bar.h" in it. To me, use of absolute paths on the #include line seems rather obscure, I'd expect relative paths, and compiler -I flags (often with absolute paths) pointing to location of relevant include directories. Regards, /Niels -- Niels Möller. PGP key CB4962D070D77D7FCB8BA36271D8F1FF368C6677. Internet email is subject to wholesale government surveillance. _______________________________________________ gmp-bugs mailing list gmp-bugs@gmplib.org https://gmplib.org/mailman/listinfo/gmp-bugs
