Build source to intall on macos bigsur (11.2.3 m1 2020) failed !!!

[wilsonliu123]

Describe the bug
When I execute "./configure " command then show the error message like this
"configure: error: no usable libjpeg; please install libjpeg devel package or equivalent"
To Reproduce

1. ./bootstrap.sh
2. ./configure
   Expected behavior

Package version or git hash

• Version [e.g. 1.10.5]

[MarioG-X]

I strongly suspect that ./bootstrap.sh and ./configure are not using the correct directory for locating homebrew packages. Homebrew on M1 now uses /opt, and non-M1 still goes to /usr/local. Freeswitch has not been updated yet to detect M1 and search /opt. See the macOS status page for M1 status.

Do a "brew list" to see if jpeg is installed, there is a homebrew arm64 version. You may want to consider using the macFI. For help post on the FreeSwitch Mailing List

[suzp1984]

I repeated this building failed problem at my macOS14 M2 chip machine.
It take me one day to overcome the building failures. I build from the source code (manual), I didn't tried the macFI, because I think libs/libvpx,freeswitch's 3rd part dependency, didn't support M1 chip (or arm64) yet, there are no way to overcome this, else to upgrade it to latest version.

Except the libvpx issue, I also did a lot patch to fix other building errors. I believe the official document of macOS manual install need to update.

1. I sent following issues/PR to fix libks building error on macOS.

signalwire/homebrew-signalwire#21
signalwire/libks#204

2. install libks-1.8.3, signalwire-c-1.3.3, sofia-sip-1.13.17, libjpeg-turbo-3.0.2 from source code and install to /usr/local/.

3. config PKG_CONFIG_PATH of homebrew's pkg-config, because there are some brew install conflict in my system. e.g. multi version of ffmpeg, while the freeswitch only support ffmpeg@4.
   export PKG_CONFIG_PATH="/opt/homebrew/opt/libpq/lib/pkgconfig:/opt/homebrew/opt/sqlite/lib/pkgconfig:/opt/homebrew/Cellar/ffmpeg@4/4.4.4_4/lib/pkgconfig/"
   maybe install openssl, libtiff manuelly too, I did some hack on the configure.ac & Makefile.am to fix the missing openssl headers.

4. disable libvpx: ./configure --disable-libvpx. The libvpx still not yet resolved.

[MarioG-X]

I was the one who created and maintained the macOS FS wiki for 12+years, I wrote macFI. However, after the wiki conversion to GitHub I no longer have update access! I asked but no dice. That means I cannot change text and cannot update the macFI (which I did here and it works fine).

GitHub documentation is MUCH harder since it requires knowledge of Markdown, which I tried to learn. Additionally, the wiki conversion to GitHub conversion lost almost every format change I had to make it look nice.

If they give me update access to the wiki someday, I would start updates soon afterward. But no more "pretty formatting". I considered making a copy in my own GitHub space and people can use that, but that's a big project due to all the links between macOS pages, and people may not find it anyway.

[Len-PGH]

@MarioG-X Everyone can still edit the FreeSWITCH docs. Please see https://github.com/signalwire/freeswitch-docs/tree/main/docs/FreeSWITCH-Explained/Installation/macOS.

You might have stumbled upon the SignalWire developer docs. Those ones are private.

[MarioG-X]

Not a stumble, and everyone can edit but only in their own repo. You cannot change the data, or could be they need a commit which is rocket science to me every time I did one. Usually took a week to figure it out. Will take a look again since it's so out of date and I would like to upload the latest macFI.

You need to understand I put a LOT of time (years) into that wiki and it's much more time consuming with the conversion to GitHub so need to evaluate the benefit.

[Len-PGH]

An easy way to edit is to edit right from the github page.

• Navigate to the page to edit then click the edit pencil at the top right.
  

---

• Make edits then click the preview button at the top left.
  

---

• This will show the edits made.
  

---

• Click the Green Commit Changes button
  

---

• Describe the changes made. make the repo name at the bottom something relevant. Then click the green Propose Changes button.
  

---

• Last you will make the Pull Request
  

---

Once the PR is merged the changes will be live.