From: Frank Schmitt <ich@frank-schmitt.net>
Cc: emacs-devel@gnu.org
Subject: Re: Build failure under Suse 10.0
Date: Tue, 31 Oct 2006 00:24:05 +0100 [thread overview]
Message-ID: <m3vem1fkve.fsf@mid.gehheimdienst.de> (raw)
In-Reply-To: <87odrt5r9q.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 30 Oct 2006 18:16:01 -0500")
Chong Yidong <cyd@stupidchicken.com> writes:
> What configure options did you use?
./configure --prefix=/export/inverness/progs
> Does an ordinary ./configure && make work?
No.
BTW: This is the report from configure:
Configured for `i686-pc-linux-gnu'.
Where should the build process find the source code? /export/inverness/cvs/emacs
What operating system and machine description files should Emacs use?
`s/gnu-linux.h' and `m/intel386.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? x11
What toolkit should Emacs use? LUCID
Where do we find X Windows header files? /usr/X11R6/include
Where do we find X Windows libraries? /usr/X11R6/lib
Does Emacs use -lXaw3d? yes
Does Emacs use -lXpm? yes
Does Emacs use -ljpeg? yes
Does Emacs use -ltiff? yes
Does Emacs use -lungif? yes
Does Emacs use -lpng? yes
Does Emacs use X toolkit scroll bars? yes
--
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.
next prev parent reply other threads:[~2006-10-30 23:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 9:53 Build failure under Suse 10.0 Frank Schmitt
2006-10-30 23:16 ` Chong Yidong
2006-10-30 23:24 ` Frank Schmitt [this message]
2006-10-30 23:49 ` Nick Roberts
2006-10-31 0:26 ` Chong Yidong
2006-10-31 4:25 ` Eli Zaretskii
2006-10-31 15:25 ` Chong Yidong
2006-11-04 13:20 ` Eli Zaretskii
2006-10-31 9:29 ` Juanma Barranquero
2006-10-31 22:15 ` Eli Zaretskii
2006-10-31 23:06 ` Chong Yidong
2006-11-01 4:17 ` Eli Zaretskii
2006-11-02 4:42 ` Richard Stallman
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=m3vem1fkve.fsf@mid.gehheimdienst.de \
--to=ich@frank-schmitt.net \
--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).