From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: 2280@emacsbugs.donarmstrong.com
Subject: bug#2280: 23.0.90; incorrect configuration
Date: Wed, 11 Feb 2009 17:39:31 +0100 [thread overview]
Message-ID: <6EA7B146-B376-472A-9DF3-FBA3AFFB5F91@Freenet.DE> (raw)
Hello!
The situation seems to be even worse than I described before! Passing
to configure "--x-includes=/opt/local/include --x-libraries=/opt/
local/lib" I see now twice the inappropriate /sw containing lines
(CVS update in-between):
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... cc -E -no-cpp-precomp -I/sw/
include -L/sw/lib
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for AIX... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether gcc understands -Wno-pointer-sign... yes
checking whether ln -s works... yes
checking how to run the C preprocessor... cc -E -no-cpp-precomp -I/sw/
include -L/sw/lib
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
and in the end configure reports:
What compiler should emacs be built with? gcc -I/sw/
include -L/sw/lib -Wno-pointer-sign -H -pipe -fPIC -mcpu=7450 -
mtune=7450 -fast -mpim-altivec -ftree-vectorize -foptimize-register-
move -freorder-blocks -freorder-blocks-and-partition -fthread-jumps -
fpeephole -fno-crossjumping
Let's see how this builds!
--
Greetings
Pete
If you don't find it in the index, look very carefully through the
entire catalogue.
– Sears, Roebuck, and Co., Consumer's Guide, 1897
next reply other threads:[~2009-02-11 16:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 16:39 Peter Dyballa [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-02 21:32 bug#2280: 23.0.90; incorrect configuration Chong Yidong
2010-01-02 22:49 ` Peter Dyballa
2010-01-10 0:11 Chong Yidong
2010-01-10 9:18 ` Peter Dyballa
2012-05-16 7:35 ` Glenn Morris
2012-05-16 12:42 ` Stefan Monnier
2009-02-11 10:42 ` Peter Dyballa
2012-05-16 17:17 ` Glenn Morris
2012-05-17 1:18 ` Stefan Monnier
2012-05-18 7:16 ` Glenn Morris
2012-05-18 16:33 ` Glenn Morris
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=6EA7B146-B376-472A-9DF3-FBA3AFFB5F91@Freenet.DE \
--to=peter_dyballa@freenet.de \
--cc=2280@emacsbugs.donarmstrong.com \
/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).