"Stinking" and "stinker" are playful terms in American English--things
you'd call your little kids when they're being cute or funny. It's more of
a playful term. In this context it expresses excitement that I found the
bug. To a non-native American English speaker, I can see the confusion. I
was very calm when I wrote it.

I can see the confusion. I took the word out.

> Can you explain concisely in which way absolute include paths made gmp
configure break in your environment?

In the answer <https://stackoverflow.com/a/77435216/4561887>, please jump
halfway down, to the section titled "Explanation of the
${gcc_srcdir_RELATIVE}/configure relative path fix that works". I can
neither explain it more nor less simply than that.

At this point I'm no longer seeking help, but rather just sharing my
findings in case it helps someone else.

Sincerely,

Gabriel Staples



On Mon, Nov 6, 2023 at 11:51 PM Niels Möller <ni...@lysator.liu.se> wrote:

> "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

Reply via email to