Follow-up Comment #27, task #16596 (group administration): [comment #26 comment #26:] > Where exactly should we "call" GNU/Linux?
Definitely, [//www.gnu.org/gnu/gnu-linux-faq.html#always we don't ask people
to call Linux GNU], that would be incorrect. What we ask is not to call GNU
Linux.
> For example, the gcc target for GNU/Linux is named "linux", so that source
> files have to use "#ifdef __linux__" and the like.
When _building_ GCC, one uses
[//www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.72/html_node/System-Types.html
Autoconf conventions] to specify the target, that is, _cpu-company-system_
where system is either _os_ or _kernel-os_, e.g. aarch64-linux-gnu. When
running GCC, the preprocessor defines some host-specific macros, and for me,
they do include __gnu_linux__:
$ cpp -dM /dev/null | grep gnu.linux
#define __gnu_linux__ 1
Have you any other specific examples?
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/task/?16596>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
signature.asc
Description: PGP signature
