From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 19111@debbugs.gnu.org
Subject: bug#19111: 25.0.50; 32 bits temacs.exe is linked with wrong image-base when built on 64 bit Windows host
Date: Fri, 21 Nov 2014 17:03:19 +0200 [thread overview]
Message-ID: <83zjbk38aw.fsf@gnu.org> (raw)
In-Reply-To: <87r3wwprln.fsf@wanadoo.es>
> From: Óscar Fuentes <ofv@wanadoo.es>
> Cc: 19111@debbugs.gnu.org
> Date: Fri, 21 Nov 2014 15:15:32 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> + t=${t#Target: }
> >
> > Is this portable to Unix shells? If not, perhaps use the 'eval' trick
> > here.
>
> This code is never meant to be executed on other than MSYS(2)/Cygwin.
> Does the shell complain if an error is present inside an `if' that it
> doesn't enter? In other words, does the shell perform syntactic checks
> on code that it doesn't execute?
It does, sometimes. I'll let experts to tell if this is one of those
cases.
>
> >> + if test "x$t" = "x"; then
> >> + AC_MSG_ERROR([Impossible to determine $cc compiler target.
> >> +Please explicitly provide --target])
> >
> > I would replace this with a warning and go with $canonical as it was
> > determined before.
>
> `configure' outputs hundreds of messages on quick succession. Warnings
> are useless for the average users (warnings just go unnoticed.) Apart
> from that, if at the user's end the script fails to get the Target from
> the compiler, we would like to know about that new compiler on
> emacs-devel/bugs (gcc 4.x and clang should work; dunno about old gcc
> versions but I expect that 3.x is fine too.)
OTOH, we've lived without this test for quites some time, so suddenly
starting to reject any configurations that might cause this sounds too
drastic to me.
next prev parent reply other threads:[~2014-11-21 15:03 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 20:27 bug#19111: 25.0.50; 32 bits temacs.exe is linked with wrong image-base when built on 64 bit Windows host Óscar Fuentes
2014-11-19 20:40 ` Eli Zaretskii
2014-11-19 21:27 ` Óscar Fuentes
2014-11-19 21:50 ` Óscar Fuentes
2014-11-19 22:01 ` Óscar Fuentes
2014-11-20 3:45 ` Eli Zaretskii
2014-11-20 3:43 ` Eli Zaretskii
2014-11-20 3:41 ` Eli Zaretskii
2014-11-20 4:10 ` Óscar Fuentes
2014-11-20 16:05 ` Eli Zaretskii
2014-11-20 16:23 ` Óscar Fuentes
2014-11-20 17:12 ` Eli Zaretskii
2014-11-20 18:30 ` Óscar Fuentes
2014-11-20 19:12 ` Dani Moncayo
2014-11-20 21:03 ` Eli Zaretskii
2014-11-21 0:07 ` Óscar Fuentes
2014-11-21 8:28 ` Eli Zaretskii
2014-11-21 14:15 ` Óscar Fuentes
2014-11-21 15:03 ` Eli Zaretskii [this message]
2014-11-21 16:06 ` Dani Moncayo
2014-11-21 17:02 ` Glenn Morris
2014-11-21 17:17 ` Dani Moncayo
2014-11-21 17:21 ` Glenn Morris
2014-11-21 18:12 ` Óscar Fuentes
2014-11-21 17:56 ` Dani Moncayo
2014-11-21 18:01 ` Dani Moncayo
2014-11-21 18:21 ` Óscar Fuentes
2014-11-21 18:34 ` Dani Moncayo
2014-11-21 18:41 ` Óscar Fuentes
2014-11-21 22:54 ` Óscar Fuentes
2014-11-22 1:05 ` Glenn Morris
2014-11-22 1:13 ` Óscar Fuentes
2014-11-25 2:38 ` Óscar Fuentes
2014-11-25 20:26 ` Dani Moncayo
2014-11-25 20:52 ` Óscar Fuentes
2014-11-25 21:13 ` Dani Moncayo
2014-11-25 23:41 ` Óscar Fuentes
2014-11-25 23:46 ` Dani Moncayo
2014-11-26 0:00 ` Óscar Fuentes
2014-11-26 3:49 ` Eli Zaretskii
2014-11-26 20:05 ` Dani Moncayo
2014-11-29 10:07 ` Dani Moncayo
2014-11-29 10:32 ` Eli Zaretskii
2014-11-29 18:22 ` Dani Moncayo
2014-11-29 18:31 ` Eli Zaretskii
2014-11-29 19:25 ` Dani Moncayo
2014-11-29 20:23 ` Eli Zaretskii
2014-11-29 20:37 ` Dani Moncayo
2014-11-29 20:52 ` Eli Zaretskii
2014-11-29 16:24 ` Óscar Fuentes
2014-11-29 18:37 ` Dani Moncayo
2014-11-29 18:49 ` Eli Zaretskii
2014-11-29 19:23 ` Dani Moncayo
2014-11-29 19:33 ` Achim Gratz
2014-11-29 19:41 ` Andreas Schwab
2014-11-29 19:45 ` Óscar Fuentes
2014-11-29 20:21 ` Eli Zaretskii
2014-11-25 23:42 ` Dani Moncayo
2014-11-22 8:46 ` Dani Moncayo
2014-11-22 10:16 ` Eli Zaretskii
2014-11-22 15:11 ` Óscar Fuentes
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=83zjbk38aw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19111@debbugs.gnu.org \
--cc=ofv@wanadoo.es \
/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.