From: Andreas Schwab <schwab@linux-m68k.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: "Andreas Röhler" <andreas.roehler@online.de>, emacs-devel@gnu.org
Subject: Re: Emacs 23.2.94 pretest
Date: Thu, 24 Feb 2011 19:56:34 +0100 [thread overview]
Message-ID: <m2lj156z31.fsf@igel.home> (raw)
In-Reply-To: <87ei6xuwxa.fsf@stupidchicken.com> (Chong Yidong's message of "Thu, 24 Feb 2011 13:09:21 -0500")
Chong Yidong <cyd@stupidchicken.com> writes:
> Andreas Röhler <andreas.roehler@online.de> writes:
>
>> in directory which contains Emacs sources alone
>> configure fails right after start:
>>
>> CFLAGS="-g -O2 -fno-optimize-sibling-calls" ./configure
>> checking build system type... i686-pc-linux-gnu
>> checking host system type... i686-pc-linux-gnu
>> checking for gcc... gcc
>> checking whether the C compiler works... yes
>> checking for C compiler default output file name... a.out
>> checking for suffix of executables...
>> checking whether we are cross compiling... configure: error: in
>> /home/My-Name/emacs-23.2.94':
>> configure: error: cannot run C compiled programs.
>> If you meant to cross compile, use `--host'.
>> See `config.log' for more details
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>>
>> Linux 2.6.31.14-0.6-default #1 SMP 2010-12-10 11:18:32 +0100 i686 i686
>> i386 GNU/Linux
>
> Anyone know what this error refers to?
See above.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2011-02-24 18:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 4:46 Emacs 23.2.94 pretest Chong Yidong
2011-02-15 4:54 ` Miles Bader
2011-02-15 15:49 ` Chong Yidong
2011-02-15 18:43 ` copyright-update in nnfolder [was Re: Emacs 23.2.94 pretest] Glenn Morris
2011-02-15 20:30 ` Stefan Monnier
2011-02-16 2:22 ` Miles Bader
2011-02-16 21:28 ` Emacs 23.2.94 pretest Lars Ingebrigtsen
2011-02-17 1:00 ` Sean Sieger
2011-02-23 17:36 ` Uday S Reddy
2011-02-23 17:44 ` Chong Yidong
2011-02-23 17:51 ` Uday S Reddy
2011-02-23 19:01 ` Chong Yidong
2011-02-23 19:27 ` Eli Zaretskii
2011-02-23 20:36 ` Uday S Reddy
2011-02-23 20:41 ` Lennart Borgman
2011-02-24 0:28 ` Christoph
2011-02-23 21:21 ` Chong Yidong
2011-02-23 21:51 ` Eli Zaretskii
2011-02-23 23:11 ` Chong Yidong
2011-02-23 23:35 ` Uday Reddy
2011-02-24 3:54 ` Eli Zaretskii
2011-02-23 23:46 ` Uday S Reddy
2011-02-23 17:59 ` Eli Zaretskii
2011-02-24 1:13 ` Sean Sieger
2011-02-24 4:01 ` Eli Zaretskii
[not found] ` <4D669A15.9080701@online.de>
2011-02-24 18:09 ` Chong Yidong
2011-02-24 18:56 ` Andreas Schwab [this message]
2011-02-24 21:26 ` Andreas Röhler
2011-02-24 22:20 ` Davis Herring
2011-02-25 6:46 ` Andreas Röhler
2011-02-25 9:32 ` Andreas Schwab
2011-02-25 10:09 ` Andreas Röhler
2011-02-25 7:01 ` Andreas Röhler
2011-02-25 13:35 ` Davis Herring
2011-02-25 10:18 ` Andreas Röhler
2011-02-25 10:29 ` Andreas Schwab
2011-02-25 11:31 ` Andreas Röhler
2011-02-25 11:43 ` Andreas Röhler
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=m2lj156z31.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=andreas.roehler@online.de \
--cc=cyd@stupidchicken.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).