From: Ryan Yeske <rcyeske@gmail.com>
To: ams@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: 22.0.98 build problem
Date: Mon, 23 Apr 2007 14:14:59 -0700 (PDT) [thread overview]
Message-ID: <20070423211459.3C296142E4@owie.localdomain> (raw)
In-Reply-To: <20070423194047.BE12630136@Psilocybe.Update.UU.SE>
I checked out emacs this morning, and on
OpenBSD bluff.my.domain 4.0 GENERIC#1056 macppc
emacs fails to build.
I couldn't reproduce it, but I'm running 3.9 here.
Indeed, it works for me on 4.0 on i386. Seems to be a OpenBSD/macppc
specific problem.
next prev parent reply other threads:[~2007-04-23 21:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 19:19 22.0.98 build problem Ryan Yeske
2007-04-23 19:40 ` Alfred M. Szmidt
2007-04-23 21:14 ` Ryan Yeske [this message]
2007-04-24 16:03 ` Richard Stallman
2007-04-26 4:16 ` Ryan Yeske
2007-04-26 7:27 ` Glenn Morris
2007-04-26 9:01 ` Ryan Yeske
2007-04-28 4:41 ` Glenn Morris
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=20070423211459.3C296142E4@owie.localdomain \
--to=rcyeske@gmail.com \
--cc=ams@gnu.org \
--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).