From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Alan Third <alan@idiocy.org>, 18743@debbugs.gnu.org
Subject: bug#18743: 25.0.50; Clang 3.0 fails to compile src/fns.c, GCC 4.8 cannot dump emacs
Date: Sun, 3 Dec 2017 20:55:15 +0100 [thread overview]
Message-ID: <AB50BF27-49D9-44C3-A64D-7FDD87D75135@Freenet.DE> (raw)
In-Reply-To: <87a7yzipi1.fsf@users.sourceforge.net>
Am 3.12.2017 um 20:24 schrieb Noam Postavsky:
> So only 3.0 fails with this, while both earlier and later versions
> succeed?
>
>> fns.c:1929:16: error: read-only variable is not assignable
>> *dest++ = *a++;
>> ~^
>>
Yes, obviously. Today I do not have Clang 3.0 installed on my MacBook (with Clang 3.7.1 and newer compilation succeeds) and neither on my old PowerBook. Also Clang 3.0 is not supported any more by MacPorts, a packet manager for GNU and other free software.
--
Greetings
Pete
"Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM."
next prev parent reply other threads:[~2017-12-03 19:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 20:52 bug#18743: 25.0.50; Clang 3.0 fails to compile src/fns.c, GCC 4.8 cannot dump emacs Peter Dyballa
2016-05-25 20:47 ` Alan Third
2016-05-25 21:40 ` Peter Dyballa
2017-12-03 19:24 ` Noam Postavsky
2017-12-03 19:41 ` Andreas Schwab
2017-12-03 19:55 ` Peter Dyballa [this message]
2017-12-03 20:01 ` Noam Postavsky
2017-12-03 20:28 ` Peter Dyballa
2017-12-03 20:46 ` Noam Postavsky
2017-12-04 3:33 ` Eli Zaretskii
2017-12-04 23:48 ` Richard Stallman
2017-12-05 8:58 ` Peter Dyballa
2017-12-05 23:13 ` Richard Stallman
2017-12-06 0:22 ` Peter Dyballa
2017-12-06 18:13 ` Richard Stallman
2017-12-06 18:21 ` Glenn Morris
2017-12-07 19:48 ` Richard Stallman
2017-12-06 18:23 ` Peter Dyballa
2017-12-06 19:40 ` Peter Dyballa
2017-12-06 18:16 ` Peter Dyballa
2017-12-07 19:52 ` Richard Stallman
2017-12-08 0:33 ` Peter Dyballa
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=AB50BF27-49D9-44C3-A64D-7FDD87D75135@Freenet.DE \
--to=peter_dyballa@freenet.de \
--cc=18743@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=npostavs@users.sourceforge.net \
/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).