Re: compiling emacs-devel on Mac OS X Lion fails

[Po Lu <luangruo@yahoo.com>]

Werner LEMBERG <wl@gnu.org> writes:

> The 'emacs-devel' package of MacPorts is currently based on commit
> 4650ea9c25514831d925e5006ea0c3679344333b (from 2022-Jul-12).
>
> On Mac OS X 10.7.5 (Lion), emacs 27.2 builds fine.  However, the above
> commit fails with
>
> ```
> ./temacs --batch  -l loadup --temacs=pbootstrap \
>          --bin-dest /opt/local/bin/ \
>          --eln-dest /opt/local/lib/emacs/29.0.50/
> Warning: arch-independent data dir
>   '/opt/local/share/emacs/29.0.50/etc/': Invalid argument
> Warning: Lisp directory
>   '/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_editors_emacs/emacs-devel/work/emacs-20220712/lisp':
>   Invalid argument
> Error: /opt/local/share/emacs/29.0.50/etc/charsets: Invalid argument
> Emacs will not function correctly without the character map files.
> ```
>
> Does this ring a bell?  I reported the problem already in
>
>   https://lists.gnu.org/archive/html/emacs-devel/2022-04/msg00803.html
>
> without progress then.  It also fails on Mountain Lion and Mavericks,
> BTW; the earliest Mac OS version that successfully builds
> 'emacs-devel' is Yosemite.
>
> For more details on the builds (including *huge* log files > 100MB
> because of zillion compilation warnings that weren't present in 27.2)
> see
>
>   https://ports.macports.org/port/emacs-devel/details/
>
>
>     Werner

What happens if you build without MacPorts, using the built-in Command
Line Developer Tools instead?