Needs to be looked at when re-doing the architecture handling.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@ignatenkobrain I agree with you.
I think showing the little or big endian information by rpm helps the debugging.
I did debug writing below code in a source directly.
I want to check it more casually.
```
+ /*
+ int n = 1;
+ if(*(char *) == 1) {
+printf("debug the system is little
Note also that adding an additional "informative" rpm macro to distro
configuration is utterly trivial (if that is all you wish) and documenting the
usage in distro packaging policy building a usage case.
Magically (and portably) detecting endianness within rpm build is trickier:
consider
Presumably you are talking about an rpm macro since there are already C macros
in .
I fail to see how knowing machine endianness in an rpm macro assists with
packaging: patches could (and likely SHOULD) be written to include
and test with a C macro rather than optionally applying a patch.
If
Big Endian machines are quite common in Fedora and developers usually have
problems with them so sometimes it is necessary to apply patch or special hack.
It would be useful to have macro to check which endian machine is used.
--
You are receiving this because you are subscribed to this
