### ImageMagick version

7.1.1

### Operating system

Linux

### Operating system, version and so on

Fedora 38, aarch64

### Description

ImageMagick 7 sets the default TIFF endianness  to big-endian (MSB) on Fedora 38 Linux aarch64, although aarch64 is a little-endian architecture.

This is caused by ImageMagick 7 using libtiff's idea of a native **bit-order**:

https://github.com/ImageMagick/ImageMagick/blob/3a1ce456f0b02d456078906897b20265a3111ab5/coders/tiff.c#L3368

NB: The concept of a native bit-order is questionable and as of now libtiff simply has the opinion that x86/x86_64 are the only architectures that have a 'native' LSB2MSB fillorder/bit-order ([see also](https://gitlab.com/libtiff/libtiff/-/issues/558)).

However, this has nothing to do with the native **byte-order**.

FWIW, nowadays most architectures are little-endian, and most bi-endian architectures are nowadays initialized to little-endian and most operating systems.

This is a regression to ImageMagick 6 where the byte-order was pushed to libtiff (unless explicitly specified):

```
  switch (endian_type)                                                                     
  {                                                                                        
    case LSBEndian: mode="wl"; break;                                                      
    case MSBEndian: mode="wb"; break;                                                      
    default: mode="w"; break;                                                              
  } 
```

See also: Fedora bug about this issue: https://bugzilla.redhat.com/show_bug.cgi?id=2195906

### Steps to Reproduce

`convert`  some png image to tiff and check its endianness with some like:

```
/usr/bin/convert out.tiff json: | grep endian
```

Expected output:

On aarch64 Linux (e.g. Fedora 38) the endianness should read LSB.

Actual output:

On aarch64 Linux (e.g. Fedora 38) the endianness reads MSB.

### Images

_No response_
TIFF default byte-order set to big-endian on little-endian aarch64 Linux
This is a GitHub Issue
repo:ImageMagick
owner:ImageMagick
Title : TIFF default byte-order set to big-endian on little-endian aarch64 Linux
Issue date:

--- start body ---
### ImageMagick version

7.1.1

### Operating system

Linux

### Operating system, version and so on

Fedora 38, aarch64

### Description

ImageMagick 7 sets the default TIFF endianness  to big-endian (MSB) on Fedora 38 Linux aarch64, although aarch64 is a little-endian architecture.

This is caused by ImageMagick 7 using libtiff's idea of a native **bit-order**:

https://github.com/ImageMagick/ImageMagick/blob/3a1ce456f0b02d456078906897b20265a3111ab5/coders/tiff.c#L3368

NB: The concept of a native bit-order is questionable and as of now libtiff simply has the opinion that x86/x86_64 are the only architectures that have a 'native' LSB2MSB fillorder/bit-order ([see also](https://gitlab.com/libtiff/libtiff/-/issues/558)).

However, this has nothing to do with the native **byte-order**.

FWIW, nowadays most architectures are little-endian, and most bi-endian architectures are nowadays initialized to little-endian and most operating systems.

This is a regression to ImageMagick 6 where the byte-order was pushed to libtiff (unless explicitly specified):

```
  switch (endian_type)                                                                     
  {                                                                                        
    case LSBEndian: mode="wl"; break;                                                      
    case MSBEndian: mode="wb"; break;                                                      
    default: mode="w"; break;                                                              
  } 
```

See also: Fedora bug about this issue: https://bugzilla.redhat.com/show_bug.cgi?id=2195906

### Steps to Reproduce

`convert`  some png image to tiff and check its endianness with some like:

```
/usr/bin/convert out.tiff json: | grep endian
```

Expected output:

On aarch64 Linux (e.g. Fedora 38) the endianness should read LSB.

Actual output:

On aarch64 Linux (e.g. Fedora 38) the endianness reads MSB.

### Images

_No response_
--- end body ---

The issue describes a misconfiguration in ImageMagick 7 where the default TIFF byte-order is incorrectly set to big-endian on a little-endian architecture (aarch64). This can lead to incorrect handling of TIFF files, potentially causing compatibility issues or data corruption when processing images. The problem is rooted in how ImageMagick interacts with libtiff, which has a flawed assumption about native bit-order for different architectures. This is a significant regression from ImageMagick 6, where the byte-order was correctly managed based on the architecture.