public inbox for guile-cvs@sourceware.org
help / color / mirror / Atom feed
From: cmm@sourceware.cygnus.com
To: guile-cvs@sourceware.cygnus.com
Subject: guile/guile-core/libguile ChangeLog guile-doc- ...
Date: Sat, 10 Jun 2000 06:24:00 -0000 [thread overview]
Message-ID: <20000610132428.4667.qmail@sourceware.cygnus.com> (raw)
CVSROOT: /cvs/guile
Module name: guile
Changes by: cmm@sourceware.cygnus.com 00/06/10 06:24:28
Modified files:
guile-core/libguile: ChangeLog guile-doc-snarf.in scmsigs.c
Log message:
* guile-doc-snarf.in: don't pipe the CPP output right into sed --
write it to the temp file first and check the CPP return code.
(I introduced this bug earlier, and this probably caused people
with non-GNU C preprocessors to get empty *.x files and not to
have the build fail right away...).
* scmsigs.c (s_scm_sigaction): guard the SIGSYS case with an ifdef
-- at least my libc5-based Linux system doesn't define SIGSYS.
next reply other threads:[~2000-06-10 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-10 6:24 cmm [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-21 8:14 cmm
2000-05-22 10:46 cmm
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=20000610132428.4667.qmail@sourceware.cygnus.com \
--to=cmm@sourceware.cygnus.com \
--cc=guile-cvs@sourceware.cygnus.com \
/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.
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).