M1 Mac chip fix

[MacPapo]

Hi @abougouffa, I created this pull request to close the issue on Mac M chips that currently doesn't compile at all because of compiler flags.

(defun disaster--arch-flags ()
  "Select the right flags depending on the right architecture."
  (if ((lambda () "Optimize for M1 family if true"
         (and (eq system-type 'darwin)
              (string= "arm64" (string-trim (shell-command-to-string "uname -m"))))))
      "-mcpu=apple-m1"
    "-march=native"))

This is the function that select the right comp flag when starting disaster.

[MacPapo]

I'm very sorry, but I still can't see any comments over the code.

[abougouffa]

They are not comments in a programming language sense (not Elisp lines starting with ;), they are code reviews. When you click on "Files changed" or here #30, you will find some remarks about two particular lines.

OR

[MacPapo]

Not having been assigned to the pull request, I can't see these comments, but from the photo I have fixed the first of the two lines. Could you send me a photo of the second line to fix?

[abougouffa]

Can you see them now?

Anyway, this is the second comment:

[abougouffa]

I can't test this as I don't have a Mac. However, I think this can cause an issue on other Mac architectures (see #22)

If the tool is named objdump on your machine, you can customize the variable when loading disaster.

(use-package disaster
  :ensure t
  :custom 
  (disaster-objdump "objdump -d -M att -Sl --no-show-raw-insn"))

[MacPapo]

On mac m1 we can't use gobjdump, we need the counterpart made for clang. I fixed that if it's a standard intel mac then gobjdump otherwise just objdump.

[abougouffa]

LGTM, merged! Thanks @MacPapo

[MacPapo]

Thank you @abougouffa for the attention and trust you have given me.

[abougouffa]

You're welcome @MacPapo. It is me who should thank you for your contribution!