From: Stefan Kangas <stefan@marxist.se>
To: Markus Triska <triska@metalevel.at>
Cc: 47249@debbugs.gnu.org, Alan Third <alan@idiocy.org>
Subject: bug#47249: 27.0.50; configure uses nextstep despite being told to use lucid
Date: Sun, 24 Oct 2021 15:32:17 -0700 [thread overview]
Message-ID: <CADwFkm=+6mFihq9Ep5N703tESbm_uER1gasvo-HMMbqggUzNOQ@mail.gmail.com> (raw)
In-Reply-To: <87r1cank4r.fsf@metalevel.at>
Markus Triska <triska@metalevel.at> writes:
> Stefan Kangas <stefan@marxist.se> writes:
>
>> Thanks. Does it work as you expect if you use --without-ns as well?
>
> No: When I add --without-ns, I now get an error (it used to work with
> the earlier Emacs version that I used to file the original issue).
>
> Specifically, the script output ends with:
>
> configure: error: You seem to be running X, but no X development libraries
> were found. You should install the relevant development files for X
> and for the toolkit you want, such as Gtk+. Also make
> sure you have development files for image handling, i.e.
> tiff, gif, jpeg, png and xpm.
> If you are sure you want Emacs compiled without X window support, pass
> --without-x
> to configure.
I am not very familiar with X builds on macOS, but I assume that you
have those headers installed? Why can't configure find them?
I copied in Alan Third, our macOS expert. (I see that he replied
separately earlier in the thread.)
next prev parent reply other threads:[~2021-10-24 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 22:21 bug#47249: 27.0.50; configure uses nextstep despite being told to use lucid Markus Triska
2021-03-18 22:50 ` Alan Third
2021-03-19 2:18 ` Glenn Morris
2021-10-21 21:19 ` Stefan Kangas
2021-10-24 19:58 ` Markus Triska
2021-10-24 21:52 ` Stefan Kangas
2021-10-24 22:16 ` Markus Triska
2021-10-24 22:32 ` Stefan Kangas [this message]
2023-09-14 18:29 ` Markus Triska
2023-09-14 19:09 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=+6mFihq9Ep5N703tESbm_uER1gasvo-HMMbqggUzNOQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=47249@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=triska@metalevel.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).