From: "Joe Corneli" <holtzermann17@gmail.com>
To: "Glenn Morris" <rgm@gnu.org>
Cc: 1358@emacsbugs.donarmstrong.com
Subject: bug#1358: error when compiling ftfont.c from CVS
Date: Thu, 20 Nov 2008 17:12:04 -0600 [thread overview]
Message-ID: <a9670630811201512t669b820erd06bdee525afae5c@mail.gmail.com> (raw)
In-Reply-To: <fn63mjhzcs.fsf@fencepost.gnu.org>
Note: I did get emacs to compile after running autoconf as you suggested.
Now I'm trying again in the same directory after 'cvs up' (I don't
know if having
previously run autoconf taints the experiment).
First piece of data:
I don't know how you guys are doing things these days, but this might
be a problem:
Merging differences between 1.303 and 1.304 into configure
rcsmerge: warning: conflicts during merge
cvs update: conflicts found in configure
...
./configure --infodir='${prefix}/share/info'
--mandir='${prefix}/share/man' --libexecdir='${prefix}/lib'
./configure: line 641: syntax error near unexpected token `<<<'
./configure: line 641: `<<<<<<< configure'
Second piece of data:
after removing ./configure, updating, and running ./configure again, I
do now get the line
checking for fontconfig >= 2.2.0... no
I assume that means it is going to work.... and yes, make bootstrap worked.
On Wed, Nov 19, 2008 at 9:04 PM, Glenn Morris <rgm@gnu.org> wrote:
>
> Does it work now, with an up-to-date copy of configure from CVS?
>
next prev parent reply other threads:[~2008-11-20 23:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <734p22kmt3.fsf@fencepost.gnu.org>
2008-11-16 23:19 ` bug#1358: error when compiling ftfont.c from CVS Joe Corneli
2008-11-17 23:56 ` Glenn Morris
2008-11-18 1:12 ` Joe Corneli
2008-11-18 1:24 ` Glenn Morris
2008-11-18 1:30 ` Processed: " Emacs bug Tracking System
2008-11-18 2:02 ` Joe Corneli
2008-11-18 2:11 ` Glenn Morris
2008-11-18 2:13 ` Glenn Morris
2008-11-20 3:04 ` Glenn Morris
2008-11-20 23:12 ` Joe Corneli [this message]
2008-11-20 23:25 ` bug#1358: marked as done (error when compiling ftfont.c from CVS) Emacs bug Tracking System
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a9670630811201512t669b820erd06bdee525afae5c@mail.gmail.com \
--to=holtzermann17@gmail.com \
--cc=1358@emacsbugs.donarmstrong.com \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.