From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: emacs-devel@gnu.org
Subject: Re: Some error info from configure.bat please
Date: Sat, 02 Jul 2005 14:32:12 +0200 [thread overview]
Message-ID: <42C6894C.5080702@student.lu.se> (raw)
In-Reply-To: <uk6k9qr58.fsf@gnu.org>
Eli Zaretskii wrote:
>>Date: Sat, 02 Jul 2005 11:32:11 +0200
>>From: Lennart Borgman <lennart.borgman.073@student.lu.se>
>>
>>Could configure.bat provide some info when something goes wrong? It is
>>enough to set an environment variable (configureerr?) to 1 for example.
>>
>>
>
>What would you like to do with that indication? (We already have
>config.log with the log of failures during configure.)
>
>
I would like to use this in a cmd file to see if the build should
continue after config.bat.
My config.log looks like this:
gcc -c junk.c
junk.c:1:29: cygwin/version.h: No such file or directory
The failed program was:
#include "cygwin/version.h"
main(){}
gcc -Id:/g/include -c junk.c
gcc -c -O2 -mtune=pentium4 junk.c
cc1.exe: invalid option `tune=pentium4'
The failed program was:
main(){}
gcc -Id:/g/include -c junk.c -o junk.obj
gcc -Id:/g/include -c junk.c -o junk.obj
gcc -Id:/g/include -c junk.c -o junk.obj
gcc -Id:/g/include -c junk.c -o junk.obj
gcc -Id:/g/include -c junk.c -o junk.obj
Does it give me any information I can check from the cmd file?
>
>
>>This would make it much easier to do supply working command files for
>>automatic building of Emacs under w32.
>>
>>
>
>What ``working command files'' are we talking about?
>
My own. I use to upload copies of them to the net.
next prev parent reply other threads:[~2005-07-02 12:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 9:32 Some error info from configure.bat please Lennart Borgman
2005-07-02 13:22 ` Eli Zaretskii
2005-07-02 12:32 ` Lennart Borgman [this message]
2005-07-02 16:53 ` Eli Zaretskii
2005-07-02 16:01 ` Lennart Borgman
2005-07-02 16:34 ` Juanma Barranquero
2005-07-02 17:36 ` Eli Zaretskii
2005-07-02 20:24 ` Jason Rumney
2005-07-02 21:16 ` Juanma Barranquero
2005-07-02 21:37 ` Jason Rumney
2005-07-02 21:45 ` Lennart Borgman
2005-07-02 22:20 ` Jason Rumney
2005-07-03 6:19 ` Eli Zaretskii
2005-07-02 21:37 ` Lennart Borgman
2005-07-03 0:22 ` Juanma Barranquero
2005-07-03 0:54 ` Lennart Borgman
2005-07-03 1:14 ` David Kastrup
2005-07-03 1:40 ` Juanma Barranquero
2005-07-03 8:19 ` David Kastrup
2005-07-03 10:42 ` Juanma Barranquero
2005-07-03 1:21 ` Juanma Barranquero
2005-07-03 6:30 ` Eli Zaretskii
2005-07-03 7:29 ` Lennart Borgman
2005-07-03 16:02 ` Eli Zaretskii
2005-07-03 7:50 ` Lennart Borgman
2005-07-03 16:11 ` Eli Zaretskii
2005-07-03 16:27 ` Juanma Barranquero
2005-07-03 18:58 ` Eli Zaretskii
2005-07-03 18:17 ` Juanma Barranquero
2005-07-04 14:54 ` Stefan Monnier
2005-07-04 15:17 ` Andreas Schwab
2005-07-04 18:07 ` Stefan Monnier
2005-07-04 18:45 ` Lennart Borgman
2005-07-16 12:39 ` Eli Zaretskii
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=42C6894C.5080702@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--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).