From: Glenn Morris <rgm@gnu.org>
To: 8642-done@debbugs.gnu.org
Subject: bug#8642: 24.0.50; cannot build on Solaris 10
Date: Tue, 17 May 2011 23:42:07 -0400 [thread overview]
Message-ID: <suoc30y8s0.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <86liyfcnuz.fsf@jimmy.4407.kankyo-u.ac.jp>
Version: 24.1
>> 3. Solaris's cc does not allow the combination of C99 option and
>> _XOPEN_SOURCE=500, for example, fakemail.c fails.
After looking into this a little bit, I think your change to 600 may be
correct. But fakemail.c was removed, so it's no longer necessary.
If that file comes back, please send a reminder about this. Thanks.
prev parent reply other threads:[~2011-05-18 3:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 2:04 bug#8642: 24.0.50; cannot build on Solaris 10 NAKAJI Hiroyuki
2011-05-12 7:23 ` Glenn Morris
2011-05-18 3:42 ` Glenn Morris [this message]
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=suoc30y8s0.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=8642-done@debbugs.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).