From: Brad Walker <me@bradmwalker.com>
To: emacs-devel@gnu.org
Subject: emacs 23.0.60; --without-x should --disable-font-backend
Date: Wed, 05 Mar 2008 04:31:32 -0700 [thread overview]
Message-ID: <1204716692.2823.8.camel@brad.office> (raw)
In the latest CVS head ./configure --without-x enables font backend and
freetype if they're detected.
[brad@brad emacs]$ ./configure --without-x
...
Configured for `x86_64-unknown-linux-gnu'.
Where should the build process find the source
code? /home/brad/emacs
What operating system and machine description files should Emacs use?
`s/gnu-linux.h' and `m/amdx86-64.h'
What compiler should emacs be built with? gcc -g -O2
-Wno-pointer-sign
Should Emacs use the GNU version of malloc? yes
(Using Doug Lea's new malloc from the GNU C Library.)
Should Emacs use a relocating allocator for buffers? yes
Should Emacs use mmap(2) for buffer allocation? no
What window system should Emacs use? none
What toolkit should Emacs use? none
Where do we find X Windows header files? NONE
Where do we find X Windows libraries? NONE
Does Emacs use -lXaw3d? no
Does Emacs use -lXpm? no
Does Emacs use -ljpeg? no
Does Emacs use -ltiff? no
Does Emacs use a gif library? no
Does Emacs use -lpng? no
Does Emacs use -lrsvg-2? no
Does Emacs use -lgpm? no
Does Emacs use -ldbus? yes
Does Emacs use a font backend? yes
Does Emacs use -lfreetype? yes
Does Emacs use -lm17n-flt? no
Does Emacs use -lotf? no
Does Emacs use -lxft? no
Does Emacs use X toolkit scroll bars? no
Building this breaks on xdisp.c:
[brad@brad emacs]$ make bootstrap
...
gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I.
-I/home/brad/emacs/src -D_BSD_SOURCE -I/usr/include/alsa
-I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -g -O2
-Wno-pointer-sign -I/usr/include/freetype2 frame.c
gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I.
-I/home/brad/emacs/src -D_BSD_SOURCE -I/usr/include/alsa
-I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -g -O2
-Wno-pointer-sign -I/usr/include/freetype2 scroll.c
gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I.
-I/home/brad/emacs/src -D_BSD_SOURCE -I/usr/include/alsa
-I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -g -O2
-Wno-pointer-sign -I/usr/include/freetype2 xdisp.c
xdisp.c: In function ‘handle_auto_composed_prop’:
xdisp.c:4596: error: ‘enable_font_backend’ undeclared (first use in this
function)
xdisp.c:4596: error: (Each undeclared identifier is reported only once
xdisp.c:4596: error: for each function it appears in.)
make[2]: *** [xdisp.o] Error 1
make[2]: Leaving directory `/home/brad/emacs/src'
make[1]: *** [bootstrap-build] Error 2
make[1]: Leaving directory `/home/brad/emacs'
make: *** [bootstrap] Error 2
"./configure --without-x --disable-font-backend" successfully builds.
Results found on Fedora Rawhide.
Brad Walker
next reply other threads:[~2008-03-05 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 11:31 Brad Walker [this message]
2008-05-20 6:38 ` emacs 23.0.60; --without-x should --disable-font-backend Kenichi Handa
2008-05-20 7:42 ` Brad Walker
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=1204716692.2823.8.camel@brad.office \
--to=me@bradmwalker.com \
--cc=emacs-devel@gnu.org \
/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).